[Spce-user] Internal IPs in INVITES

chrismeadows chris at simplephoneco.com
Thu Jun 13 19:06:52 EDT 2013


Hello.

We have an interesting an issue on we have been trying to troubleshoot that only happens with incoming calls from a peer/provider, but not outbound. (in and out with our 2 other major carriers does not have this issue)

In short, in INVITE or something shows there internal IPs in the call setups on our server, which in turn creates an unauthorized 407 error on our end and the incoming calls fails. (See logs). We have been going back and forth with them on this, and they advised us to whitelist their internal IPs (they have 9 /24 blocks they sent us, a lot of IPs…) and that there isn't anything they can do about it. (They are a fairly big PULC here in the US...) What would be the best direction to work around this. Here is the log as an example:

++++++

INVITE sip:+19494821234 at 198.199.117.240 SIP/2.0
Record-Route: <sip:67.231.8.195;lr=on;ftag=gK0c2ebbd6>
Record-Route: <sip:67.231.4.93;lr=on;ftag=gK0c2ebbd6>
Accept: application/sdp
Allow: INVITE,ACK,CANCEL,BYE
Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK4599.2979beb6.0
Via: SIP/2.0/UDP 67.231.4.93;branch=z9hG4bK4599.436d2253.1
Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK0cBad7c10c031d9d83e
From: <sip:+14804268161 at 192.168.47.68;isup-oli=0>;tag=gK0c2ebbd6
To: <sip:+19494821234 at 67.231.4.93>
Call-ID: 1947004952_133806585 at 192.168.47.68
CSeq: 27025 INVITE
Max-Forwards: 137
Contact: <sip:+14804268161 at 192.168.47.68:5060>
Content-Length: 327
Content-Disposition: session; handling=required
Content-Type: application/sdp
Remote-Party-ID: <sip:+14804268161 at 192.168.47.68:5060>;privacy=off;screen=no

v=0
o=Sonus_UAC 2284 14966 IN IP4 192.168.47.68
s=SIP Media Capabilities
c=IN IP4 67.231.4.99
t=0 0
m=audio 10134 RTP/AVP 0 18 96 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:96 iLBC/8000
a=fmtp:96 mode=30
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=maxptime:30

Tue Jun 04 16:49:55 GMT-400 2013 198.199.117.240:5060 --> 67.231.8.195:5060

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 67.231.8.195;rport=5060;branch=z9hG4bK4599.2979beb6.0
Via: SIP/2.0/UDP 67.231.4.93;branch=z9hG4bK4599.436d2253.1
Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK0cBad7c10c031d9d83e
From: <sip:+14804268161 at 192.168.47.68;isup-oli=0>;tag=gK0c2ebbd6
To: <sip:+19494821234 at 67.231.4.93>
Call-ID: 1947004952_133806585 at 192.168.47.68
CSeq: 27025 INVITE
Server: Sipwise NGCP Proxy 2.X
Content-Length: 0


Tue Jun 04 16:49:55 GMT-400 2013 198.199.117.240:5060 --> 67.231.8.195:5060

SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 67.231.8.195;rport=5060;branch=z9hG4bK4599.2979beb6.0
Via: SIP/2.0/UDP 67.231.4.93;branch=z9hG4bK4599.436d2253.1
Via: SIP/2.0/UDP 192.168.47.68:5060;branch=z9hG4bK0cBad7c10c031d9d83e
From: <sip:+14804268161 at 192.168.47.68;isup-oli=0>;tag=gK0c2ebbd6
To: <sip:+19494821234 at 67.231.4.93>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.0b31
Call-ID: 1947004952_133806585 at 192.168.47.68
CSeq: 27025 INVITE
Proxy-Authenticate: Digest realm="192.168.47.68", nonce="Ua5UH1GuUvOlgvzfjZTt9JnMJovyDZEj"
Server: Sipwise NGCP Proxy 2.X
Content-Length: 0

++++++++

Thank you in advance for any and all help.

Chris



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20130613/0d845189/attachment.html>


More information about the Spce-user mailing list