SIP Softswitch Real Addr vs Gave Addr
-
We are working hard on troubleshooting a networking issue and we have been given this snippet of data from the trunk provider's softswitch, which we are inclined to believe is a Cisco, but that's not a definite.
# ovly ckt CKT000 > list iltg 51 PKT TG 51 STATUS=INS ACTV CALLS=0 GAVE ADDR:201.45.53.67:5060 REAL ADDR:201.45.53.67:1032 RENEWS EVERY: 1800 SECONDSHas anyone worked with a softswitch that uses this syntax? My belief here is that gave address is the address expected to be used for a response. Real Address is the port that the router had to use because sending ports are almost always random and isn't relevant to anything in reality. But this isn't a syntax you can look up given the information that we have at hand. So I am hoping that someone can eye ball this.
-
Here is additional information we were given. A packet capture on their end of the SIP headers:
Via: SIP/2.0/UDP 201.45.53.67:5060;branch=z9hG4bK583ca6e0;rport
Max-Forwards: 70
From: sip:[email protected];tag=as2c743cc9
To: sip:[email protected]
Call-ID: [email protected]
CSeq: 154 REGISTER
User-Agent: FPBX-2.11.0(11.14.2)
Authorization: Digest username="user", realm="sip.provider.com", algorithm=MD5, uri="sip:sip.provider.com", nonce="201.45.53.67", response="7f9c9cb3f38d2a262f33869f6171d238", qop=auth, cnonce="717a598b", nc=00000034
Expires: 120
Contact: sip:[email protected]:5060
Content-Length: 0From: sip:[email protected];tag=as2c743cc9
To: sip:[email protected];tag=f897ad48-cc0e38ca-13c4-6006-ea019c-6c08ad76-ea019c
Call-ID: [email protected]
CSeq: 154 REGISTER
Contact: sip:[email protected]:5060;expires=1794
Via: SIP/2.0/UDP 201.45.53.67:5060;rport=1032;branch=z9hG4bK583ca6e0
Supported: 100rel,replaces,timer
Content-Length: 0Via: SIP/2.0/UDP 201.45.53.67:5060;branch=z9hG4bK1857f536;rport
Max-Forwards: 70
From: sip:[email protected];tag=as2c743cc9
To: sip:[email protected]
Call-ID: [email protected]
CSeq: 155 REGISTER
User-Agent: FPBX-2.11.0(11.14.2)
Authorization: Digest username="user", realm="sip.provider.com", algorithm=MD5, uri="sip:sip.provider.com", nonce="201.45.53.67", response="3e373ba013b0fd62c0baa86a566c0d48", qop=auth, cnonce="61dba914", nc=00000035
Expires: 120
Contact: sip:[email protected]:5060
Content-Length: 0From: sip:[email protected];tag=as2c743cc9
To: sip:[email protected];tag=f8869610-cc0e38ca-13c4-6006-ea088f-77415d06-ea088f
Call-ID: [email protected]
CSeq: 155 REGISTER
Contact: sip:[email protected]:5060;expires=1795
Via: SIP/2.0/UDP 201.45.53.67:5060;rport=1032;branch=z9hG4bK1857f536
Supported: 100rel,replaces,timer
Content-Length: 0As Scott said, note the rport value. It sticks out because it's a lower number, but it is random. Let me know if I'm looking at this right if you guys can.
-
@scottalanmiller said in SIP Softswitch Real Addr vs Gave Addr:
GAVE ADDR:201.45.53.67:5060 REAL ADDR:201.45.53.67:1032
Where did you run the command from in the original post? (#ovly cky) CKT000 ???
Provider may be using a Cisco switch, and IKE encryption given that lower port number?
-
@bigbear said in SIP Softswitch Real Addr vs Gave Addr:
@scottalanmiller said in SIP Softswitch Real Addr vs Gave Addr:
GAVE ADDR:201.45.53.67:5060 REAL ADDR:201.45.53.67:1032
Where did you run the command from in the original post? (#ovly cky) CKT000 ???
Provider may be using a Cisco switch, and IKE encryption given that lower port number?
They wouldn't tell us, hence the complications.
-
I am not sure how this will relate,.. but I am staring at our PBX and and this page. And then I see the different port numbers - It's interesting to see so many that are not 5060
Name/username Host Dyn Forcerport Comedia ACL Port Status Description 7101/7101 SomeIpHere D Yes Yes A 1418 OK (126 ms) 7102/7102 SomeIpHere D Yes Yes A 1126 OK (87 ms) 7103/7103 SomeIpHere D Yes Yes A 5062 OK (83 ms) 7104/7104 SomeIpHere D Yes Yes A 1360 OK (72 ms) 7105 (Unspecified) D Yes Yes A 0 UNKNOWN 7106 (Unspecified) D Yes Yes A 0 UNKNOWN 7107/7107 SomeIpHere D Yes Yes A 1498 OK (134 ms) 7108 (Unspecified) D Yes Yes A 0 UNKNOWN 7109/7109 SomeIpHere D Yes Yes A 1369 OK (62 ms) 7110/7110 SomeIpHere D Yes Yes A 1536 OK (74 ms) 7111/7111 SomeIpHere D Yes Yes A 5060 OK (136 ms) 7112/7112 SomeIpHere D Yes Yes A 1037 OK (85 ms) 7113/7113 SomeIpHere D Yes Yes A 1038 OK (97 ms) 7114/7114 SomeIpHere D Yes Yes A 1396 OK (133 ms) 7202/7202 SomeIpHere D Yes Yes A 1108 OK (73 ms) 7203 (Unspecified) D Yes Yes A 0 UNKNOWN 7204/7204 SomeIpHere D Yes Yes A 1357 OK (299 ms) 7205/7205 SomeIpHere D Yes Yes A 1033 OK (168 ms) 7207 (Unspecified) D Yes Yes A 0 UNKNOWN 7208/7208 (Unspecified) D Yes Yes A 0 UNKNOWN 7210/7210 SomeIpHere D Yes Yes A 1030 OK (170 ms) 7211/7211 SomeIpHere D Yes Yes A 1024 OK (138 ms) 7212/7212 SomeIpHere D Yes Yes A 1092 OK (62 ms) -
@gjacobse said in SIP Softswitch Real Addr vs Gave Addr:
I am not sure how this will relate,.. but I am staring at our PBX and and this page. And then I see the different port numbers - It's interesting to see so many that are not 5060
No relation. this is NAT networking 101.
All of your devices connect to pbx.ntg.co:5060
But their local outbound ports cannot all be 5060. How would the router know which devices to translate it back to. -
@jaredbusch said in SIP Softswitch Real Addr vs Gave Addr:
@gjacobse said in SIP Softswitch Real Addr vs Gave Addr:
I am not sure how this will relate,.. but I am staring at our PBX and and this page. And then I see the different port numbers - It's interesting to see so many that are not 5060
No relation. this is NAT networking 101.
All of your devices connect to pbx.ntg.co:5060
But their local outbound ports cannot all be 5060. How would the router know which devices to translate it back to.Yup,. I get that. - well anyway. moving right along...
