Hello,
I'm using sipp as a subscriber: it sends SUBSCRIBE's to a server and
receives NOTIFY's from the server. The transport used is TCP.
In a typical scenario I will have two tcp connections:
- Connection 1: One ongoing connection from the sipp-subscriber through
which SUBSCRIBE's are sent to the server and responses to these SUBSCRIBE's
are received. (1)
- Connection 2: One incoming connection from the server to the
sipp-subscriber port I put in the Contact header of the SUBSCRIBE, through
which NOTIFY's are received from the server and responses to these NOTIFYS's
are sent. (2)
I have noticed that if the Server closes the Connection 1, the
sipp-subscriber starts sending SUBSCRIBE through the Connection 2. Is this
the expected behaviour??
Best regards
Santi
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users