Thank you tcp_accept_aliases = 1 work/
2013/5/27 Bogdan-Andrei Iancu :
> Hello Chusov,
>
> The presence modules disable the opening of new TCP conns for sequential
> requests (like NOTIFIES) as they follow the same TCP conn as the SUBSCRIBE.
>
> What I see on your trace is that SUBSCRIBE comes fro
Hello Chusov,
The presence modules disable the opening of new TCP conns for sequential
requests (like NOTIFIES) as they follow the same TCP conn as the SUBSCRIBE.
What I see on your trace is that SUBSCRIBE comes from 10.222.1.253:37827
, but the advertised address in Contact hdr is
sip:@10.22
Sorry send wrong trace
T 2013/05/23 13:24:13.215773 10.222.1.253:37827 -> 10.222.0.17:5060 [AP]
SUBSCRIBE sip:2...@g-voip.stb.ua SIP/2.0.
Via: SIP/2.0/TCP 10.222.1.253:5060;branch=z9hG4bK1334330933;rport;alias.
From: ;tag=1005928247.
To: .
Call-ID: 310582788-5060...@ba.ccc.b.cfd.
CSeq: 20070 SUBSCR
The registration info is used only for routing the SUBSCRIBE (which is
ok). For the NOTIFY routing, the info from SUBSCRIBE + its 200 OK is
used - this is why I need the pcap.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 05/22/2013 08:24 PM, C
I do not have pcap because use TLS. But I can tomorrow create pcap TCP.
Two phone one enable "Use Actual Ephemeral Port in Contact with TCP/TLS" (
2...@g-voip.stb.ua )
AOR:: 9...@g-voip.stb.ua
Contact:: sip:@10.222.1.253:5060;transport=tls Q=
Ex
Hi Chusov,
The NOTIFY is sent back to the IP:port from the Contact in received
SUBSCRIBE. Do you have a pcap capture of the SUBSCRIBE + NOTIFY on the
opensips side ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 05/22/2013 06:12 PM, Chusov Ale
Hello
I have Grandstream phone with setup BLF button.
Opensips use for REGISTER|Presence|BLF
When set Grandstream options to "Use Actual Ephemeral Port in Contact
with TCP/TLS" phone add to Contact header port to which it is
connected BLF work fine.
But if phone set port to standard 5060 Opensips