[Spce-user] Rewrite Question

[Martin Wong]

Hi Lorenzo,

I think it's not going through the rewrite rule itself.

I've hardcoded the rewrite rule to say

^123456789 -> 12345678900 (for example)

and it didn't even catch it.

Is it because I've manually updated the template to register the peer?

Martin Wong
Director at Binary Elements
http://www.binaryelements.com.au
Tel: 03 9005 8880
DID: 03 9020 7907
Mob: 0405 817 796


On Fri, Apr 19, 2013 at 4:14 PM, Lorenzo Mangani
<lorenzo.mangani at gmail.com>wrote:

> Hi Martin,
>
> Share the rules you attempted to use to rewrite to E.164 on the list, the
> problem is most likely still there.
>
> Best,
>
> Lorenzo Mangani
>
> HOMER DEV TEAM
> QXIP - Network Engineering
>
> On Fri, Apr 19, 2013 at 7:36 AM, Martin Wong <
> martin.wong at binaryelements.com.au> wrote:
>
>> Hi,
>>
>> I got a peer registered with authentication, so had to change the
>> reg_agent.conf.tt2 per the doc.
>>
>> All good and I can see the calls coming in when I do a ngrep
>>
>> Problem is that this provider doesn't send the numbers over as E.164
>> Number. Instead, it just leaves the country code out.
>>
>> I tried to capture this via the Inbound Caller Rewrite Rules but it seems
>> that the number is not getting parsed through that. I've ensured the peer
>> is using the correct rewrite rule set but still no go.
>>
>> I suspect that it's not getting parsed through there.
>>
>> I was also trying to update the Alias numbers in the subscriber but it
>> only accepts the E.164 format.
>>
>> Any idea what I can do here?
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
>>
>
>
> --
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130419/2bf1917b/attachment-0001.html>