3 Feb
2005
3 Feb
'05
4:25 p.m.
Hey Jan,
I've forwarded the same info off to the Vendor (incl. full packet dumps
from ngrep) to see what they say, but perhaps it's something with my
rewriting code. Anything you see that's not as it should be.
# 7 digit call - append area code of caller
if (uri=~"^sip:[0-9]{7}\@.*") {
exec_dset("
/bin/echo -n 'sip:' > /tmp/.areacode.$$;
/bin/echo -n $SIP_HF_CONTACT | /bin/cut -c '2 3 4' | /bin/tr -d
'\n' >> /tmp/.areacode.$$;
/bin/echo $SIP_RURI | awk -F'sip:' '{print $2}' >>
/tmp/.areacode.$$;
/bin/cat /tmp/.areacode.$$;
/bin/rm -f /tmp/.areacode.$$;
echo>/dev/null;
");
};
# 10 digit call - append 1
if (uri=~"^sip:[0-9]{10}\@.*") {
prefix("1");
};
-Evan
On Thu, 2005-02-03 at 13:37 +0100, Jan Janak wrote:
What gateway are you using ? It should perform no
checks of the
Record-Route header field because it does not belong to the gateway,
this particular header field was inserted by SER.
Are you sure that it is the Record-Route header field what gets rejected
? Maybe there is some problem in the request-uri ?
Jan.
On 02-02 15:48, Evan Borgstrom wrote:
> Hey all,
>
> I've implemented re-writing of URI's based on 7 & 10 digit numbers
fine
> in SER but the problem is that our gateway that connects us to the PSTN
> lines is doing verification on the Record-Route headers. So when I
> rewrite 5551212 into 12345551212 the INVITE message shows the following
> and the PSTN gateway returns a 404 not found because it cant forward
> 5551212 to the PSTN.
>
>
> INVITE sip:12345551212@1.1.1.4:5060 SIP/2.0.
> Record-Route: <sip:5551212@1.1.1.2;ftag=4b2deae9ab74b4ebo0;lr=on>.
>
> Is there anyway to rewrite the Record-Route part of the headers?
>
>
> -Evan
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers