30 Aug
2005
30 Aug
'05
7:39 p.m.
Ah,
Seems unreasonable to require From/To formatting, unfortunately,
at least one company I can think of does that.
Anyway, you will need to either properly format
the from/to at the origin (presumably the UAC) or
you will need a b2bua in the signal path to modify those
fields. Unfortunately, you CANNOT change anything in
the message EXCEPT the RURI. You can add information.
The From/To/Callid form a key for the message.
That said, you could change the From/To, and sometimes things
will continue to work because there are other 'keys' for the message.
But it would not be proper.
I don't believe vanilla SER will accomplish what you
desire. Perhaps you could put Asterisk in the signaling path?
---greg
On 8/30/05, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote:
Ryan Tucker wrote:
--
Greg Fausak
greg(a)thursday.com
Greetings...
We are starting to work with a carrier which requires From: and To: to
be in E.164 format (e.g. +17005551212). prefix() only seems to change
the INVITE, which doesn't appear to cut the mustard with these guys. Is
there any way to make this happen within SER?
Thanks! -rt
Hi Ryan!
This is not the "SIP-way". To and From can't be changed by SIP proxies.
The PSTN provider should route the calls according the to number in the
request URI. For setting the CLI, the suggested way is the
Remote-Party-Id header, which was invented by Cisco and is supported by
Cisco, Inalp and asterisk.
klaus
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers