Hi guys,

Forget to modify the From and TO headers, it's not rfc compliant and furthermore, u will have lots of problems with Uacs. We have that done for a non compliant provider (Icallglobe) and we had so many problems that we have changed of provider... For example: User typed 0033xxxxxxxx, u strip the 00 in the Invite and in the TO, Uac will probably not recognise the transaction and will not rignback...

The best way is to change of provider.

Olivier

-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Ryan Tucker Envoyé : mercredi 31 août 2005 15:16 À : Pietro Ravasio Cc : serusers@lists.iptel.org Objet : Re: [Serusers] Adding +1 to From:/To: for E.164 compliance

Pietro Ravasio wrote:

I suggest you to use textops module and subst functions, for example:

loadmodule "/your/path/to/textops.so" ... subst_uri('/^sip:([0-9]*@.*)/sip:+1\1/i');

You can change anything within the body of a message, using subst instead of subst_uri

This seems really dirty and ugly, yet appears to be doing the trick without breaking things. Thanks!

Thanks as well to Klaus and Greg; I fully agree that this is an abomination, and may very well involve the same carrier Greg is thinking of. I've got Asterisk around for any cases where this doesn't work out, so we'll see how it goes. -rt

Greg Fausak wrote:

I'm heading out to VON this year, I'd love to put some faces to names. Anybody else going? I'll be there Sep 20-22.

I will be there (at the standing of enum.at and Telekom Austria).

regards klaus

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@pernau.at wrote:

Ryan Tucker wrote:

...

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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers