You should also take a look as to why proxy thinks its external port is
55060. sipx only supports synchronized firewall ports.
----------
INVITE sip:11404@192.168.1.110:2048;line=5nrfoelc SIP/2.0
Record-Route:
<sip:50.18.193.48:55060;lr;sipXecs-CallDest=AL%2CINT;sipXecs-rs=%2Aauth%7E.%2Afrom%7EMzgwNDkxMTE5.900_ntap%2ACeT%7EOTIuMjM2LjIwNS4xMjk6MjA0ODt0cmFuc3BvcnQ9dWRw.900_ntap%2Aid%7EMjAzNzMtMA%60%60%2128138fba7fd68124d4eded66c1678824>
Call-Id: bee104006623-50e810fd-729c9139-3b5e9008-8c3a119@127.0.0.1-0
Cseq: 21048 INVITE
From: <sip:07956426802@194.145.191.131>;tag=380491119
To: <sip:442079028126@50.18.193.48>
Via: SIP/2.0/UDP
50.18.193.48:55060;branch=z9hG4bK-XX-0170DDOcpkNfBxxzhT_mRjgLUA
Via: SIP/2.0/TCP
10.7.7.30;branch=z9hG4bK-XX-0166tZbEyCarg`T124rYCvoO8g~zuDoDrbxRIzA0ui5ZR`i1g;id=20373-0
Via: SIP/2.0/UDP
10.7.7.30;branch=z9hG4bK-XX-015fNDSZeEEhmvz0OaCVm`Z6DQ~7XWJm7VD9wRzaVDa3eWsKg
Via: SIP/2.0/UDP
10.7.7.30:5090;branch=z9hG4bK0c5f3d31ceea5cafd4b3547d07291689353537;sipxecs-id=83c6eea
Max-Forwards: 16
User-Agent: sipXecs/4.4.0 sipXecs/sipxbridge (Linux)
References:
bee104006623-50e810fd-729c9139-3b5e9008-8c3a119@127.0.0.1;rel=chain;sipxecs-tag=request-invite-z9hg4bkc839.cc38c0d1.0
Contact: <sip:2079028126@10.7.7.30:5090;x-sipX-nonat>
Content-Type: application/sdp
Allow: INVITE,BYE,ACK,CANCEL,REFER,OPTIONS,PRACK
Supported: replaces,100rel
Content-Length: 243
Date: Sat, 05 Jan 2013 11:39:43 GMT
Alert-Info: <http://external.call>;info=alert-external;x-line-id=0
Expires: 25
X-Sipx-Nat-Route: 92.236.205.129:2048;transport=udp
X-Sipx-Handled: X10.7.7.30-50.18.193.48
v=0
o=sipxbridge 7742502536895419624 1 IN IP4 10.7.7.30
s=session
c=IN IP4 10.7.7.30
t=0 0
m=audio 30498 RTP/AVP 8 0
c=IN IP4 50.18.193.48
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=sendrecv
a=x-sipx-ntap:X10.7.7.30-50.18.193.48;0
On 01/07/2013 11:42 PM, Sven Evensen wrote:
Two colleagues just tried that and it work!! Thanks again Tony!!
On Mon, Jan 7, 2013 at 3:39 PM, Tony Graziano
<tgrazi...@myitdepartment.net <mailto:tgrazi...@myitdepartment.net>>
wrote:
You should disable gruu on the snom.
On Jan 7, 2013 10:24 AM, "Sven Evensen" <sven.even...@onrelay.com
<mailto:sven.even...@onrelay.com>> wrote:
Thanks for a few good tips Tony. The outbound calls work fine,
it is only the inbound call which fails. It is because
sipxProxy is relaying ACK to the internal IP of the phone,
wrong of course. I have looked at the REGISTER and the only
field I can see which differs from the soft phone (which works
fine) is "X-Real-IP" which does contain the internal IP
REGISTER sip:ec2-50-18-193-48.us-west-1.compute.amazonaws.com
<http://ec2-50-18-193-48.us-west-1.compute.amazonaws.com> SIP/2.0
Via: SIP/2.0/UDP
192.168.1.110:2048;branch=z9hG4bK-ccn6pkaxxrrw;rport
From: "Dwayne Kee"
<sip:11...@ec2-50-18-193-48.us-west-1.compute.amazonaws.com
<mailto:sip%3a11...@ec2-50-18-193-48.us-west-1.compute.amazonaws.com>>;tag=rgiklqr928
To: "Dwayne Kee"
<sip:11...@ec2-50-18-193-48.us-west-1.compute.amazonaws.com
<mailto:sip%3a11...@ec2-50-18-193-48.us-west-1.compute.amazonaws.com>>
Call-ID: 386d43a0edbb-qfxd1lgiuetf
CSeq: 2 REGISTER
Max-Forwards: 70
Contact:
<sip:11404@192.168.1.110:2048;line=v2kaaktt>;q=1.0;reg-id=1;+sip.instance="<urn:uuid:<urn:uuid:5f98f7c3-7423-49e4-a3fe-4d25402cdfa6>>";audio;mobility="fixed";duplex="full";description="snom300";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"
User-Agent: snom300/8.7.3.15 <http://8.7.3.15>
Allow-Events: dialog
X-Real-IP: 192.168.1.110
Supported: path, gruu
Authorization: Digest
username="11404",realm="ec2-50-18-193-48.us-west-1.compute.amazonaws.com
<http://ec2-50-18-193-48.us-west-1.compute.amazonaws.com>",nonce="448038dd4fbe27452d637428dc1a565950e76936",uri="sip:ec2-50-18-193-48.us-west-1.compute.amazonaws.com
<http://ec2-50-18-193-48.us-west-1.compute.amazonaws.com>",qop=auth,nc=00000001,cnonce="35993a6f",response="ad299e3bc739b3d5882f39ea7a64e04f",algorithm=MD5
Expires: 3600
Content-Length: 0
On Mon, Jan 7, 2013 at 2:39 PM, Tony Graziano
<tgrazi...@myitdepartment.net
<mailto:tgrazi...@myitdepartment.net>> wrote:
it might be more pertinent to post a sanitized config of
the phone. As
I recall the snom's dont configure "the same" as a polycom
(SRV
records, etc.). I also know there is a patch just
committed for Snom
on 4.6, so you might ask the devs (Domenico authored the
patch) about
what was changed, and why.
I "think" you have to disable GRUU on snom. I am confused
as to why
the snom says it is not behind NAT when the server is in
EC3 or
wherever. The phone registration should show more helpful
information.
It would appear (to me) the phone is not configured
correctly and
sending its private address on outbound calls.
On Mon, Jan 7, 2013 at 9:25 AM, Sven Evensen
<sven.even...@onrelay.com
<mailto:sven.even...@onrelay.com>> wrote:
> Our sipx 4.4 is running in Amazon, we have mostly mobile
externsion (our
> product) and soft phones and a few IP phones. The
Polycoms we have no issue
> with. But we have now installed 3 SNOMs and all three
have then problem that
> incoming calls all disconnect after half a minute or
so.Outbound calls are
> fine
>
> From the trace I can see the 200 OK from the phone is
relayed back to the
> SIP trunk, then the ACK from the SIP trunk is not
relayed back to the phone,
> but to SipxRegistrar where it stops up.
>
> I have attached the sip trace for this. Also a sip trace
for a soft phone on
> the same user which does not have this issue.
>
> Also worth mentioning that one SNOMis configured from
the template in sipX,
> another (which is attached) is configured from the
phone, in the same was as
> a soft phone. Same issue on both phones.
>
> --
>
> Sven Evensen, Operations Consultant
>
> OnRelay
>
> +44 (0) 207 902 8123
<tel:%2B44%20%280%29%20207%20902%208123> ?
mailto:sven.even...@onrelay.com
<mailto:sven.even...@onrelay.com> ? www.onrelay.com
<http://www.onrelay.com>
>
>
> This electronic message transmission contains
information from OnRelay,
> Ltd., that may be confidential or privileged. The
information is intended
> solely for the recipient and use by any other party is
not authorised. If
> you are not the intended recipient, be aware that any
disclosure, copying,
> distribution or use of the contents of this information
or any attachment,
> is prohibited. If you have received this electronic
transmission in error,
> please notify us immediately by electronic mail
(i...@onrelay.com <mailto:i...@onrelay.com>) and
> delete this message, along with any attachments, from
your computer.
> Registered in England No 04006093 ¦ Registered Office
1st Floor, 236 Gray's
> Inn Road, London WC1X 8HB
>
>
> _______________________________________________
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
<mailto:sipx-users@list.sipfoundry.org>
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430 <tel:434.984.8430>
sip: tgrazi...@voice.myitdepartment.net
<mailto:tgrazi...@voice.myitdepartment.net>
Fax: 434.465.6833 <tel:434.465.6833>
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~
Using or developing for sipXecs from SIPFoundry? Ask me
about sipX-CoLab 2013!
--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426 <tel:434.984.8426>
sip: helpd...@voice.myitdepartment.net
<mailto:helpd...@voice.myitdepartment.net>
Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
<mailto:sipx-users@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
*Sven Evensen, Operations Consultant*
*OnRelay*
+44 (0) 207 902 8123 <tel:%2B44%20%280%29%20207%20902%208123>
? mailto:sven.even...@onrelay.com ? www.onrelay.com
<http://www.onrelay.com/>
This electronic message transmission contains information from
OnRelay, Ltd., that may be confidential or privileged. The
information is intended solely for the recipient and use by
any other party is not authorised. If you are not the intended
recipient, be aware that any disclosure, copying, distribution
or use of the contents of this information or any attachment,
is prohibited. If you have received this electronic
transmission in error, please notify us immediately by
electronic mail (i...@onrelay.com <mailto:i...@onrelay.com>)
and delete this message, along with any attachments, from your
computer. Registered in England No 04006093 ¦ Registered
Office 1st Floor, 236 Gray's Inn Road, London WC1X 8HB
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
<mailto:sipx-users@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426 <tel:434.984.8426>
sip: helpd...@voice.myitdepartment.net
<mailto:helpd...@voice.myitdepartment.net>
Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org <mailto:sipx-users@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
*Sven Evensen, Operations Consultant*
*OnRelay*
+44 (0) 207 902 8123 ? mailto:sven.even...@onrelay.com ?
www.onrelay.com <http://www.onrelay.com/>
This electronic message transmission contains information from
OnRelay, Ltd., that may be confidential or privileged. The information
is intended solely for the recipient and use by any other party is not
authorised. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this
information or any attachment, is prohibited. If you have received
this electronic transmission in error, please notify us immediately by
electronic mail (i...@onrelay.com <mailto:i...@onrelay.com>) and
delete this message, along with any attachments, from your computer.
Registered in England No 04006093 ¦ Registered Office 1st Floor, 236
Gray's Inn Road, London WC1X 8HB
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
