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