Hi Surya,
As the NOTIFY is an in-dialog request (for the dialog created by the
SUBSCRIBE request), it will be routed by OpenSIPS to the SIP contact
advertised in th SUBSCRIBER request - does the SIP URI in the Contact
header advertise the TCP transport protocol ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 22.12.2015 07:27, surya wrote:
Hi,
I am testing opensips presence server 1.8.3 using sipp. I am using TCP as
the transport. When I send SUBSCRIBE, 200 OK is received fine but the NOTIFY
is sent on UDP.
When testing from 2 SIP clients it works fine on TCP. Is there something
special to take care while testing TCP from SIPP?
Below is the command and scenario file.
*./sipp 192.168.192.131 -t t1 -sf sn.xml -m 1 -i 192.168.192.128*
-------------------------------------------------
<?xml version="1.0" encoding="ISO-8859-1" ?>
<scenario name="subscribe">
<send start_rtd="1">
</send>
<recv response="200">
</recv>
<recv request="NOTIFY" rtd="1">
</recv>
<send crlf="true">
</send>
</scenario>
-------------------------------------------------
I am not able to figure out what the problem is. I suspect it is something
to do with sipp but not sure.
I couldn't find anything on internet, hence, posting here.
Thanks,
Surya
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Getting-NOTIFY-on-UDP-while-using-transport-as-TCP-tp7600288.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________
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
