[Serusers] Adding +1 to From:/To: for E.164 compliance

Olivier Taylor olivier.taylor at gmail.com
Wed Aug 31 15:47:10 CEST 2005


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 at iptel.org [mailto:serusers-bounces at lists.iptel.org] De la
part de Ryan Tucker
Envoyé : mercredi 31 août 2005 15:16
À : Pietro Ravasio
Cc : serusers at 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

-- 
Ryan S. Tucker
Network Engineer
ISP Direct, Inc.
1159 Pittsford-Victor Road
Building 5, Suite 140
Pittsford, New York 14534
+1 585.419.8200
http://www.isp-direct.com/
http://www.vocal-net.net/

The information contained in this message may be privileged, confidential,
and protected from disclosure. If the reader of this message is not the
intended recipient, or any employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this communication is strictly
prohibited. If you have received this communication in error, please notify
us immediately by replying to the message and deleting it from your
computer. Thank you.


_______________________________________________
Serusers mailing list
serusers at lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers




More information about the sr-users mailing list