Our VoIP service provider routes calls based upon the To field within the SIP header. While SER can easily rewrite the URI, I need to actually prepend our account code to every outgoing call with a prefix. does anyone know how to prefix the To field
Eric Dean writes:
Our VoIP service provider routes calls based upon the To field within the SIP header. While SER can easily rewrite the URI, I need to actually prepend our account code to every outgoing call with a prefix. does anyone know how to prefix the To field.
it is not a good idea to modify to or from fields. i suggest you switch to another, more sensible service provider.
-- juha
I also have two providers using the to header.
Why is it a bad idea to modify the to and from fields?
Olivier
-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Juha Heinanen Envoyé : vendredi 15 avril 2005 15:31 À : Eric Dean Cc : serusers@lists.iptel.org Objet : [Serusers] Rewrite To Heaader
Eric Dean writes:
Our VoIP service provider routes calls based upon the To field within the SIP header. While SER can easily rewrite the URI, I need to actually prepend our account code to every outgoing call with a prefix. does anyone know how to prefix the To field.
it is not a good idea to modify to or from fields. i suggest you switch to another, more sensible service provider.
-- juha
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
It's a bad idea because they are used for transaction matching and if you alter either then you run the risk of a SIP UAC or SIP UAS freaking out.
Regards, Paul
On 4/15/05, Olivier Taylor olivier.taylor@gmail.com wrote:
I also have two providers using the to header.
Why is it a bad idea to modify the to and from fields?
Olivier
-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Juha Heinanen Envoyé : vendredi 15 avril 2005 15:31 À : Eric Dean Cc : serusers@lists.iptel.org Objet : [Serusers] Rewrite To Heaader
Eric Dean writes:
Our VoIP service provider routes calls based upon the To field within the SIP header. While SER can easily rewrite the URI, I need to actually prepend our account code to every outgoing call with a prefix. does anyone know how to prefix the To field.
it is not a good idea to modify to or from fields. i suggest you switch to another, more sensible service provider.
-- juha
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
putting aside the fact that modifying FROM and TO is something not so trivial, routing calls based on TO hdr is totally wrong - according to SIP RFC, the request routing is done based on RURI + ROUTE set; not to mention that TO hdr contains irrelevant information which may (most of the time) differ from the RURI. as Juha said, try to go for a more SIP compliant provider.
bogdan
Juha Heinanen wrote:
Eric Dean writes:
Our VoIP service provider routes calls based upon the To field within the SIP header. While SER can easily rewrite the URI, I need to actually prepend our account code to every outgoing call with a prefix. does anyone know how to prefix the To field.
it is not a good idea to modify to or from fields. i suggest you switch to another, more sensible service provider.
-- juha
Ok
You say anyway that routing has to be based on RURI + ROUTE
What do you think about the next line?
-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Bogdan-Andrei Iancu Envoyé : vendredi 15 avril 2005 16:34 À : Juha Heinanen Cc : Eric Dean; serusers@lists.iptel.org Objet : Re: [Serusers] Rewrite To Heaader
putting aside the fact that modifying FROM and TO is something not so trivial, routing calls based on TO hdr is totally wrong - according to SIP RFC, the request routing is done based on RURI + ROUTE set; not to mention that TO hdr contains irrelevant information which may (most of the time) differ from the RURI. as Juha said, try to go for a more SIP compliant provider.
bogdan
Juha Heinanen wrote:
Eric Dean writes:
Our VoIP service provider routes calls based upon the To field within the SIP header. While SER can easily rewrite the URI, I need to actually prepend our account code to every outgoing call with a prefix.
does anyone know how to prefix the To field.
it is not a good idea to modify to or from fields. i suggest you switch to another, more sensible service provider.
-- juha
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Ok
You say anyway that routing has to be based on RURI + ROUTE
What do you think about the next line?
INVITE sip:3227321073@217.206.202.126:5060 SIP/2.0..Record-Route: sip:027321073@82.146.123.252;ftag=8f19be0298e5a67o0;lr=on
I must suppose that Record-Route has to be used or in this case Route seems wrong.
Olivier
-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Bogdan-Andrei Iancu Envoyé : vendredi 15 avril 2005 16:34 À : Juha Heinanen Cc : Eric Dean; serusers@lists.iptel.org Objet : Re: [Serusers] Rewrite To Heaader
putting aside the fact that modifying FROM and TO is something not so trivial, routing calls based on TO hdr is totally wrong - according to SIP RFC, the request routing is done based on RURI + ROUTE set; not to mention that TO hdr contains irrelevant information which may (most of the time) differ from the RURI. as Juha said, try to go for a more SIP compliant provider.
bogdan
Juha Heinanen wrote:
Eric Dean writes:
Our VoIP service provider routes calls based upon the To field within the SIP header. While SER can easily rewrite the URI, I need to actually prepend our account code to every outgoing call with a prefix.
does anyone know how to prefix the To field.
it is not a good idea to modify to or from fields. i suggest you switch to another, more sensible service provider.
-- juha
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
please don't make the confusion between Record-Route and Route headers! Record-Route is used to set (to define) the routing set in the initial phase of the dialog creation - no routing is performed based RR hdr; the Route header is used for that purpose.
bogdan
Olivier Taylor wrote:
Ok
You say anyway that routing has to be based on RURI + ROUTE
What do you think about the next line?
INVITE sip:3227321073@217.206.202.126:5060 SIP/2.0..Record-Route: sip:027321073@82.146.123.252;ftag=8f19be0298e5a67o0;lr=on
I must suppose that Record-Route has to be used or in this case Route seems wrong.
Olivier
-----Message d'origine----- De : serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] De la part de Bogdan-Andrei Iancu Envoyé : vendredi 15 avril 2005 16:34 À : Juha Heinanen Cc : Eric Dean; serusers@lists.iptel.org Objet : Re: [Serusers] Rewrite To Heaader
putting aside the fact that modifying FROM and TO is something not so trivial, routing calls based on TO hdr is totally wrong - according to SIP RFC, the request routing is done based on RURI + ROUTE set; not to mention that TO hdr contains irrelevant information which may (most of the time) differ from the RURI. as Juha said, try to go for a more SIP compliant provider.
bogdan
Juha Heinanen wrote:
Eric Dean writes:
Our VoIP service provider routes calls based upon the To field within the SIP header. While SER can easily rewrite the URI, I need to actually prepend our account code to every outgoing call with a prefix.
does anyone know how to prefix the To field.
it is not a good idea to modify to or from fields. i suggest you switch to another, more sensible service provider.
-- juha
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Bogdan-Andrei Iancu -
Eric Dean -
Java Rockx -
Juha Heinanen -
Olivier Taylor