[Spce-user] Fwd: 404

[Skyler]

I don't have that in my box but off the top of my head (not tested) would
look something like:

^([2-9][0-9]{8})$  ${caller_cc}\1

or

^([2-9][0-9]{8})$   1\1


Skyler

On Tue, Nov 13, 2012 at 8:53 AM, Jeremie Chism <jchism2 at gmail.com> wrote:

> Do you have a standard rewrite rule for this.  I am going to ask my
> upstream but not sure i will get much of a reply.
>
>
> On Tue, Nov 13, 2012 at 10:49 AM, Skyler <skchopperguy at gmail.com> wrote:
>
>> No problem. Just for future, this type of issue really only need to see
>> the INVITE and not necessarily the whole call flow in a capture. ;)
>>
>> The R=sip:3184504920 is the problem because SPCE bases all routing
>> decisions on the R-URI (Request URI) which is what the 'R' in the logs is.
>>
>> S
>>
>> On Tue, Nov 13, 2012 at 8:44 AM, Jeremie Chism <jchism2 at gmail.com> wrote:
>>
>>> 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
>>>>
>>>>
>>>
>
>
> --
> Jeremie Chism
> Triton Communications
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121113/a87bb5e9/attachment-0001.html>