Re: [OpenSIPS-Users] tcp_blocking_connect for same ip but different listen port

2015-05-12 Thread Bogdan-Andrei Iancu
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

[OpenSIPS-Users] tcp_blocking_connect for same ip but different listen port

2015-05-08 Thread Gupta, Rahul
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