Re: [Serusers] rewrite the From part of SIP INVITE messages

List overview All Threads
Download

newer

older

[Serusers] Proxy Authentication

[Users] An error with exec_msg

rcarvalho＠iric.up.pt

26 Aug 2006 26 Aug '06

8:55 p.m.

I'm sceptic about the use of functions that replace parts of SIP messages, because that way, will Ser still keep record of transactions? Wont those replacements affect Ser to recognise to whom route subsequent messages? Regards, Ricardo. Alexandr Dubovikov wrote:

...

On Fri, Aug 25, 2006 at 05:33:52PM +0100, Ricardo Carvalho wrote:

I need to rewrite the From part of SIP INVITE messages before sending them to my IP Telco, or else they wont accept my calls! Anyone knows how can I do that?

replace or subst the sample you can find in README file of textops module.

Thanks, Ricardo. _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Show replies by date

Alexandr Dubovikov

26 Aug 26 Aug

10:20 p.m.

New subject: [Serusers] rewrite the From part of SIP INVITE messages

On Sat, Aug 26, 2006 at 07:55:41PM +0100, rcarvalho(a)iric.up.pt wrote:

...

I'm sceptic about the use of functions that replace parts of SIP messages, because that way, will Ser still keep record of transactions? Won?t those replacements affect Ser to recognise to whom route subsequent messages? Regards, Ricardo.

Yep, we already discused here about it one week ago. From, To and Call-ID make a Call Leg of transaction. I am not sure, but ser tm based only on Call-ID and ignore To/From fields. Wbr, -- Alexandr Dubovikov * baron@iRC RusNet * mailto:shurik@start4.info AD1-UANIC * ICQ: 122351182 * http://www.start4.info

Greger V. Teigre

28 Aug 28 Aug

9:37 a.m.

New subject: [Serusers] rewrite the From part of SIP INVITE messages

...

On Sat, Aug 26, 2006 at 07:55:41PM +0100, rcarvalho(a)iric.up.pt wrote:

Yep, we already discused here about it one week ago. From, To and Call-ID make a Call Leg of transaction. I am not sure, but ser tm based only on Call-ID and ignore To/From fields. Wbr,

Ricardo Carvalho

2:22 p.m.

New subject: [Serusers] rewrite the From part of SIP INVITE messages

I've used subst() function for substituting From and To URIs and calls succeed well! I think that this indicates that Ser uses in fact only the Call-Id to keep track of calls and not as well From and To tags of messages. Although I agree... this may end up biting me later... It got to be a question of compromises between pros and cons! Greetings, Ricardo. Greger V. Teigre wrote:

...

NEVER manipulate From/To so that tag=something disappears!! Per RFC3261, a dialog is the combination of these two tags and Call-Id. On branching and reINVITE, the Call-Id will stay the same, while the tags may change. This is relevant for accounting, for keeping track of branches, failures, and is absolutely necessary for the UAs to recognize the dialog. The old RFC uses the full content of From/To for the same purposes, thus manipulating From/To will break your backwards suport for UACs/UASs that do not support RFC3261. This means that in a closed-wall deployment and all UAS/UAC support RFC3261, you MAY manipulate From/To, but it's not recommended and may well end up biting you later... g-) Alexandr Dubovikov wrote: > On Sat, Aug 26, 2006 at 07:55:41PM +0100, rcarvalho(a)iric.up.pt wrote: > >> I'm sceptic about the use of functions that replace parts of SIP messages, >> because that way, will Ser still keep record of transactions? Won?t those >> replacements affect Ser to recognise to whom route subsequent messages? >> >> Regards, >> >> Ricardo. >> > > Yep, we already discused here about it one week ago. From, To and Call-ID make a > Call Leg of transaction. I am not sure, but ser tm based only on Call-ID and > ignore To/From fields. > > > > Wbr, >

Greger V. Teigre

5:23 p.m.

New subject: [Serusers] rewrite the From part of SIP INVITE messages

Your subst command probably preserve the tag (as it should). If not, you would definitely get a problem... g-) Ricardo Carvalho wrote:

...

NEVER manipulate From/To so that tag=something disappears!! Per RFC3261, a dialog is the combination of these two tags and Call-Id. On branching and reINVITE, the Call-Id will stay the same, while the tags may change. This is relevant for accounting, for keeping track of branches, failures, and is absolutely necessary for the UAs to recognize the dialog. The old RFC uses the full content of From/To for the same purposes, thus manipulating From/To will break your backwards suport for UACs/UASs that do not support RFC3261. This means that in a closed-wall deployment and all UAS/UAC support RFC3261, you MAY manipulate From/To, but it's not recommended and may well end up biting you later... g-) Alexandr Dubovikov wrote: > On Sat, Aug 26, 2006 at 07:55:41PM +0100, rcarvalho(a)iric.up.pt wrote: > >> I'm sceptic about the use of functions that replace parts of SIP >> messages, >> because that way, will Ser still keep record of transactions? Won?t >> those >> replacements affect Ser to recognise to whom route subsequent >> messages? >> >> Regards, >> >> Ricardo. >> > > Yep, we already discused here about it one week ago. From, To and > Call-ID make a Call Leg of transaction. I am not sure, but ser tm > based only on Call-ID and > ignore To/From fields. > > > > Wbr, >

_______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

6642

days inactive

6644

days old

sr-users@lists.kamailio.org

Manage subscription

4 comments

4 participants

tags (0)

participants (4)

Alexandr Dubovikov
Greger V. Teigre
rcarvalho＠iric.up.pt
Ricardo Carvalho