[Spce-user] Fwd: 404

Jeremie Chism jchism2 at gmail.com
Tue Nov 13 11:44:20 EST 2012


My email was probably going out as you were sending yours.


On Tue, Nov 13, 2012 at 10:42 AM, Skyler <skchopperguy at gmail.com> wrote:

> Jeremy,
>
>  Slow down, read your INVITE.
> .....
> INVITE sip:3184504920 at 107.7.157.250 SIP/2.0'
>
> Also in the log.....R=sip:3184504920 at 107.7.157.250<3184504920 at 107.7.157.250>
>
> What Jon is saying is that clearly, 3184504920 is NOT a valid number on
> your SPCE box. Your peer is sending you a request for 10-digits but SPCE
> only uses 11-digits. You need to either ask upstream to send you e164
> (11-digits) or you need a rewrite rule that matches 10-digits and ... adds
> a 1 in front.
>
> Skyler
> On Tue, Nov 13, 2012 at 8:30 AM, Jeremie Chism <jchism2 at gmail.com> wrote:
>
>> I think that was because of the other sip trunk.  Here is a call from
>> outside that shows the 11 digits.  I will also get the log
>>
>> U 2012/11/13 10:26:52.752766 72.21.14.34:5060 -> 107.7.157.250:5060
>> INVITE sip:3184504920 at 107.7.157.250 SIP/2.0'
>> Record-Route: <sip:72.21.14.34:5060;lr;ftag=gK0e4d1028>'
>> Via: SIP/2.0/UDP 72.21.14.34:5060;branch=z9hG4bKda97.26bf9577.0'
>> Via: SIP/2.0/UDP 4.55.2.227:5060;branch=z9hG4bK0eB65610582c008d865'
>> From: <sip:+13185374776 at 4.55.2.227:5060;isup-oli=62>;tag=gK0e4d1028'
>> To: <sip:+13184504920 at 72.21.14.34:5060>'
>> Call-ID: 1494152095_4459626 at 4.55.2.227'
>> CSeq: 31124 INVITE'
>> Max-Forwards: 92'
>> Allow: INVITE,ACK,CANCEL,BYE,PRACK,UPDATE'
>> Accept: application/sdp, application/isup, application/dtmf,
>> application/dtmf-relay,  multipart/mixed'
>> Contact: <sip:+13185374776 at 4.55.2.227:5060>'
>> Remote-Party-ID: <sip:+13185374776 at 4.55.2.227:5060>;privacy=off'
>> Supported: 100rel'
>> Content-Length:  301'
>> Content-Disposition: session; handling=required'
>> Content-Type: application/sdp'
>> '
>> v=0'
>> o=Sonus_UAC 21391 635 IN IP4 4.55.2.227'
>> s=SIP Media Capabilities'
>> c=IN IP4 4.55.2.198'
>> t=0 0'
>> m=audio 10912 RTP/AVP 0 8 18 101'
>> a=rtpmap:0 PCMU/8000'
>> a=rtpmap:8 PCMA/8000'
>> a=rtpmap:18 G729/8000'
>> a=fmtp:18 annexb=no'
>> a=rtpmap:101 telephone-event/8000'
>> a=fmtp:101 0-15'
>> a=sendrecv'
>> a=maxptime:20'
>>
>> #
>> U 2012/11/13 10:26:52.753655 127.0.0.1:5060 -> 127.0.0.1:5062
>> INVITE sip:3184504920 at 107.7.157.250 SIP/2.0'
>> Record-Route: <sip:127.0.0.1:5060;ngcplb=yes;ftag=gK0e4d1028;lr=on>'
>> Record-Route: <sip:107.7.157.250:5060;ftag=gK0e4d1028;lr=on>'
>> Record-Route: <sip:72.21.14.34:5060;lr;ftag=gK0e4d1028>'
>> Via: SIP/2.0/UDP
>> 107.7.157.250;branch=z9hG4bKda97.268836150cfcef249ce40b85d56fda0e.0'
>> Via: SIP/2.0/UDP 72.21.14.34:5060
>> ;rport=5060;branch=z9hG4bKda97.26bf9577.0'
>> Via: SIP/2.0/UDP 4.55.2.227:5060;branch=z9hG4bK0eB65610582c008d865'
>> From: <sip:+13185374776 at 4.55.2.227:5060;isup-oli=62>;tag=gK0e4d1028'
>> To: <sip:+13184504920 at 72.21.14.34:5060>'
>> Call-ID: 1494152095_4459626 at 4.55.2.227'
>> CSeq: 31124 INVITE'
>> Max-Forwards: 91'
>> Allow: INVITE,ACK,CANCEL,BYE,PRACK,UPDATE'
>> Accept: application/sdp, application/isup, application/dtmf,
>> application/dtmf-relay,  multipart/mixed'
>> Contact: <sip:+13185374776 at 4.55.2.227:5060>'
>> Remote-Party-ID: <sip:+13185374776 at 4.55.2.227:5060>;privacy=off'
>> Supported: 100rel'
>> Content-Length:  301'
>> Content-Disposition: session; handling=required'
>> Content-Type: application/sdp'
>> P-NGCP-Src-Ip: 72.21.14.34'
>> P-NGCP-Src-Port: 5060'
>> P-NGCP-Src-Proto: udp'
>> P-NGCP-Src-Af: 4'
>> '
>> v=0'
>> o=Sonus_UAC 21391 635 IN IP4 4.55.2.227'
>> s=SIP Media Capabilities'
>> c=IN IP4 4.55.2.198'
>> t=0 0'
>> m=audio 10912 RTP/AVP 0 8 18 101'
>> a=rtpmap:0 PCMU/8000'
>> a=rtpmap:8 PCMA/8000'
>> a=rtpmap:18 G729/8000'
>> a=fmtp:18 annexb=no'
>> a=rtpmap:101 telephone-event/8000'
>> a=fmtp:101 0-15'
>> a=sendrecv'
>> a=maxptime:20'
>>
>> #
>> U 2012/11/13 10:26:52.753784 127.0.0.1:5062 -> 127.0.0.1:5060
>> SIP/2.0 100 Trying'
>> Via: SIP/2.0/UDP
>> 107.7.157.250;branch=z9hG4bKda97.268836150cfcef249ce40b85d56fda0e.0;rport=5060;received=127.0.0.1'
>> Via: SIP/2.0/UDP 72.21.14.34:5060
>> ;rport=5060;branch=z9hG4bKda97.26bf9577.0'
>> Via: SIP/2.0/UDP 4.55.2.227:5060;branch=z9hG4bK0eB65610582c008d865'
>> From: <sip:+13185374776 at 4.55.2.227:5060;isup-oli=62>;tag=gK0e4d1028'
>> To: <sip:+13184504920 at 72.21.14.34:5060>'
>> Call-ID: 1494152095_4459626 at 4.55.2.227'
>> CSeq: 31124 INVITE'
>> Server: Sipwise NGCP Proxy 2.X'
>> Content-Length: 0'
>> '
>>
>> #
>> U 2012/11/13 10:26:52.753916 107.7.157.250:5060 -> 72.21.14.34:5060
>> SIP/2.0 100 Trying'
>> Via: SIP/2.0/UDP 72.21.14.34:5060
>> ;rport=5060;branch=z9hG4bKda97.26bf9577.0'
>> Via: SIP/2.0/UDP 4.55.2.227:5060;branch=z9hG4bK0eB65610582c008d865'
>> From: <sip:+13185374776 at 4.55.2.227:5060;isup-oli=62>;tag=gK0e4d1028'
>> To: <sip:+13184504920 at 72.21.14.34:5060>'
>> Call-ID: 1494152095_4459626 at 4.55.2.227'
>> CSeq: 31124 INVITE'
>> Server: Sipwise NGCP Proxy 2.X'
>> Content-Length: 0'
>> '
>>
>> #
>> U 2012/11/13 10:26:52.764368 127.0.0.1:5062 -> 127.0.0.1:5060
>> SIP/2.0 404 Not Found'
>> Via: SIP/2.0/UDP
>> 107.7.157.250;branch=z9hG4bKda97.268836150cfcef249ce40b85d56fda0e.0;rport=5060;received=127.0.0.1'
>> Via: SIP/2.0/UDP 72.21.14.34:5060
>> ;rport=5060;branch=z9hG4bKda97.26bf9577.0'
>> Via: SIP/2.0/UDP 4.55.2.227:5060;branch=z9hG4bK0eB65610582c008d865'
>> From: <sip:+13185374776 at 4.55.2.227:5060
>> ;isup-oli=62>;tag=gK0e4#######################################################
>>
>>
>> On Tue, Nov 13, 2012 at 10:14 AM, Jon Bonilla <jbonilla at sipwise.com>wrote:
>>
>>> El Tue, 13 Nov 2012 10:08:12 -0600
>>> Jeremie Chism <jchism2 at gmail.com> escribió:
>>>
>>>
>>> > Subscriber 13184504920 at 107.7.157.250
>>> > E.164 Number: +1 318 4504920
>>>
>>> That doesn't match '3184504920'
>>>
>>> You need to fix your rewrite rules. As I said before, you have rewrite
>>> rules for
>>> caller (see your proxy logs) which are wrong and no matching rewrite
>>> rules for
>>> what you receive which is '3184504920'
>>>
>>> That's why the system does not find the subscriber and sends 404 back.
>>>
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>
>>
>> --
>> Jeremie Chism
>> Triton Communications
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
>>
>


-- 
Jeremie Chism
Triton Communications
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121113/8b9ad371/attachment-0001.html>


More information about the Spce-user mailing list