[Serusers] add parameters to the Record-Route - sr-users

Greger V. Teigre

12 Oct 12 Oct

11:51 a.m.

You can do as the nat configs of Getting Started document: wait with record_route() until you know which parameters you want to add (by setting some flags) and then use ifs to record_route with the correct parameter(s). It's a workaround, but it works. g-) Ricardo Carvalho wrote:

...

I need to add a parameter to the Record-Route of some sip messages, but with 0.9.6 version of Ser I guess there aren't functions implemented to do that , doesn't it? what do you recommend me? Thanks, Ricardo. _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Reply

Greger V. Teigre

3:12 p.m.

Adding record-route parameters only apply to messages you record-route. If you don't record route, you don't see further transactions, and then you don't need to set the flag, right? g-) Ricardo Carvalho wrote:

...

Ok, I done like you told me, and apparently it's already working like it should, although I have to ask you if one solution like this, adding a new Record-Route field (IP:port;flag) when I just wanted to add a flag (I don't have the need to add IP and port) isn't risky, and somewhat in the future it won't end up biting me? Regards, Ricardo. Greger V. Teigre wrote:

You can do as the nat configs of Getting Started document: wait with record_route() until you know which parameters you want to add (by setting some flags) and then use ifs to record_route with the correct parameter(s). It's a workaround, but it works. g-) Ricardo Carvalho wrote:

I need to add a parameter to the Record-Route of some sip messages, but with 0.9.6 version of Ser I guess there aren't functions implemented to do that , doesn't it? what do you recommend me? Thanks, Ricardo. _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Reply

Greger V. Teigre

13 Oct 13 Oct

9:27 a.m.

You're right and that's why I specified that you should wait with record_route until you know which parameter(s) to set. You should only record_route once. g-) Ricardo Carvalho wrote:

...

Right, I agree, but my concern is that in my ser.cfg there is already one call to the record_route() function in the route{} block, which adds the following entry in sip messages: Record-Route: <sip:172.16.103.241;ftag=1097252116;lr=on> Although, even so, using record_route_preset("172.16.103.241:5060;vm=no"); like I'm doing now just to be able to use my "vm=no" flag, in only one hop interaction of that message through Ser, this message leaves Ser with two Record-Routes like this: Record-Route: <sip:172.16.103.241;ftag=1097252116;lr=on> Record-Route: <sip:4115@172.16.103.241:5060;vm=no;ftag=1097252116;lr=on> Isn't this dangerous having two RR header fields per hop in Ser? Thanks once again, Ricardo. Greger V. Teigre wrote:

Adding record-route parameters only apply to messages you record-route. If you don't record route, you don't see further transactions, and then you don't need to set the flag, right? g-) Ricardo Carvalho wrote:

Ok, I done like you told me, and apparently it's already working like it should, although I have to ask you if one solution like this, adding a new Record-Route field (IP:port;flag) when I just wanted to add a flag (I don't have the need to add IP and port) isn't risky, and somewhat in the future it won't end up biting me? Regards, Ricardo. Greger V. Teigre wrote:

You can do as the nat configs of Getting Started document: wait with record_route() until you know which parameters you want to add (by setting some flags) and then use ifs to record_route with the correct parameter(s). It's a workaround, but it works. g-) Ricardo Carvalho wrote: > I need to add a parameter to the Record-Route of some sip > messages, but with 0.9.6 version of Ser I guess there aren't > functions implemented to do that , doesn't it? what do you > recommend me? > > Thanks, > Ricardo. > > > _______________________________________________ > Serusers mailing list > Serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > >

Reply