[Spce-user] Rewrite Question

[Andreas Granig]

Hi,

Well, in which header field your provider is sending you the called 
number then? A ngrep-sip trace would be good for such a call.

And yes, you should consider changing your provider. If it already does 
SUCH stupid things, I don't want to know how more advanced things are 
being handled (or not) then.

Andreas

On 05/01/2013 06:46 AM, Martin Wong wrote:
> Hi Daniel, the stupid provider doesn't want to change their settings.
>
> Anyway of working around this restriction and hack it on our end?
>
> 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 10:12 PM, Daniel Grotti <dgrotti at sipwise.com
> <mailto:dgrotti at sipwise.com>> wrote:
>
>     Hi Martin,
>
>     the problem here is the R-URI sent by your peer:
>
>
>     New request - M=INVITE R=sip:42.136.11.129:5060
>     <http://42.136.11.129:5060>
>
>
>     it is malformed (R=sip:42.136.11.129:5060
>     <http://42.136.11.129:5060>) it doesn't contain the user part.
>     This is why SPCE fail to fetch the callee and fails to apply
>     Rewrite-rules.
>
>     br,
>     Daniel
>
>
>
>
>     On 04/19/2013 02:03 PM, Martin Wong wrote:
>      > New request - M=INVITE R=sip:42.136.11.129:5060
>     <http://42.136.11.129:5060> <http://42.136.11.129:5060>
>
>     _______________________________________________
>     Spce-user mailing list
>     Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>     http://lists.sipwise.com/listinfo/spce-user
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>