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, Chusov Alexsandr wrote: > 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" ( [email protected] <mailto:[email protected]> ) > > AOR:: [email protected] <mailto:[email protected]> > Contact:: sip:[email protected]:5060;transport=tls Q= > Expires:: 247 > Callid:: [email protected] > Cseq:: 2053 > User-agent:: Grandstream GXP2120 1.0.5.24 > State:: CS_SYNC > Flags:: 0 > Cflag:: 0 > Socket:: tls:10.222.0.17:5061 > <http://10.222.0.17:5061> > Methods:: 6015 > AOR:: [email protected] <mailto:[email protected]> > Contact:: sip:[email protected]:45266;transport=tls Q= > Expires:: 88 > Callid:: [email protected] > Cseq:: 2047 > User-agent:: Grandstream GXP1405 1.0.5.15 > State:: CS_SYNC > Flags:: 0 > Cflag:: 0 > Socket:: tls:10.222.0.17:5061 > <http://10.222.0.17:5061> > Methods:: 6015 > > I also asked a friend to test the asterisk. He send NOTIFY to port is > connected to not Contact. > > > > 2013/5/22 Bogdan-Andrei Iancu <[email protected] > <mailto:[email protected]>> > > 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 Alexsandr wrote: > > 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 cant send NOTIFY > > > > Phone - > SUBSCRIBE -> Opensips > > Opensips -> Ok - > Phone > > Opensips -> NOTIFY -> tcp_send failed > > > > On phone log i don't see problem. He send SUBSCRIBE received OK. > About > > NOTIFY nothing. > > > > > > DBG:presence:send_notify_request: built notify_body 0x10d16f0 > > DBG:presence:send_notify_request: headers:#012Event: > > dialog#015#012Contact: > > <sip:[email protected]:5061;transport=tls>#015#012Subscription-State: > > active;expires=180#015#012Content-Type: > > application/dialog-info+xml#015#012 > > DBG:presence:build_dlg_t: CONTACT = > sip:[email protected]:5060;transport=tls > > DBG:presence_dialoginfo:dlginfo_body_setversion: set version > > DBG:presence_dialoginfo:dlginfo_body_setversion: replace version > with "0" > > DBG:tm:t_uac: next_hop=<sip:[email protected]:5060;transport=tls> > > DBG:core:mk_proxy: doing DNS lookup... > > DBG:tm:dlg2hash: 650 > > DBG:tm:print_request_uri: sip:[email protected]:5060;transport=tls > > ERROR:tm:msg_send: tcp_send failed > > ERROR:tm:t_uac: attempt to send to > > 'sip:[email protected]:5060;transport=tls' failed > > DBG:tm:set_timer: relative timeout is 5 > > DBG:tm:insert_timer_unsafe: [0]: 0x7f9a7d7b0fe0 (34) > > INFO:presence:send_notify_request: NOTIFY sip:[email protected] > <mailto:sip%[email protected]> via > > sip:[email protected]:5060;transport=tls on behalf of > > sip:[email protected] <mailto:sip%[email protected]> for > event dialog, > > to_tag=6b081e8cb2be0cc593bdd08e52ae2811-c7c2, cseq=1 > > DBG:tm:t_unref: UNREF_UNSAFE: [0x7f9a7d7a5cc0] after is 0 > > DBG:core:destroy_avp_list: destroying list (nil) > > DBG:core:receive_msg: cleaning up > > > > > > Thanks in advance > > Sorry for my English > > > > _______________________________________________ > > Users mailing list > > [email protected] <mailto:[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
