Hi Rahul,
What presence event is there ? Maybe the Notifies (first and second) are
the result of the same event and triggered from the same process (this
explaining the serial processing of them).
What OpenSIPS version are you using ? as normally, for sequential
presence requests, the opening of new TCP conns is forbidden.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 08.05.2015 19:56, Gupta, Rahul wrote:
One of the UAC changed its listen port from 5060 to 5070 and sent a
new subscription however before the subscription made it to UAS, UAS
sent a NOTIFY to UAC to port 5060 and then immediately another NOTIFY
to UAC to port 5070
Old setup:
UAC (5060) <---> opensips(proxy) (5060) <---> UAS (5059)
New Setup:
UAC (5070) <---> opensips(proxy) (5060) <---> UAS (5059)
Opensips attempted to forward the first NOTIFY to UAC at port 5060
which obviously timed out with tcp connect failed as expected
First NOTIFY :
NOTIFY sip:user1@IPADDRESS:5060;transport=tcp SIP/2.0
Opensips sent the 2^nd NOTIFY after 10 seconds to UAC at port 5070. If
the port specified in SIP URI is different then why the second request
is put into the queue and had to wait for 10 sec blocking timeout ?
Seconf NOTIFY:
NOTIFY sip:user1@IP_ADDRESS:5070;transport=tcp SIP/2.0
Is there any flag/param I can specify in my opensips.cfg file to fix
this ?
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
DISCLAIMER: This e-mail may contain information that is confidential,
privileged or otherwise protected from disclosure. If you are not an
intended recipient of this e-mail, do not duplicate or redistribute it
by any means. Please delete it and any attachments and notify the
sender that you have received it in error. Unintended recipients are
prohibited from taking action on the basis of information in this
e-mail.E-mail messages may contain computer viruses or other defects,
may not be accurately replicated on other systems, or may be
intercepted, deleted or interfered with without the knowledge of the
sender or the intended recipient. If you are not comfortable with the
risks associated with e-mail messages, you may decide not to use
e-mail to communicate with IPC. IPC reserves the right, to the extent
and under circumstances permitted by applicable law, to retain,
monitor and intercept e-mail messages to and from its systems.
_______________________________________________
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
