Hi
Please refer to https://github.com/OpenSIPS/opensips/issues/833 .
As per documentation, the 0x1 flag became obsolete, as sending the
100Trying is no longer linked to the t_relay() - the 100Trying is now
sent when the transaction is created.
If you want to disable the auto 100Trying, see the new TM flag
auto_100trying:
http://www.opensips.org/html/docs/modules/2.2.x/tm.html#id294523
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 18.06.2016 16:49, Denis wrote:
Re: [OpenSIPS-Users] TM flag 0x01 not working in 1.11.7 Hello!
2.1 has the same problem
//mailto:[email protected]
In my script I send all “100 Trying” responses manually* and use the
0x01 flag when calling t_relay so that it will not send its own “100
Giving a try” response, as per the documentation [1].
Unfortunately, in 1.11.7 and 1.11.8 this flag seems to have stopped
working which results in multiple 100 responses.
This should be easily reproducible with a script that simply calls
t_relay with flag 0x01. You will see that a “100 Giving a try”
response is still sent.
[1] http://www.opensips.org/html/docs/modules/1.11.x/tm.html#id294528
* I do this because I don’t like that the default is to send the
non-standard response “100 Giving a try” instead of “100 Trying”. I’ve
always wondered why this is that way. Additionally, the automatic
response to CANCEL requests is “200 canceling” instead of the standard
“200 OK”. Unfortunately, I have yet to find a way to workaround the
behavior for CANCEL.
Ben Newlin
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
