[SR-Users] kamailio asterisk NOTIFY

Slava Bendersky volga629 at networklab.ca
Thu Mar 12 00:36:21 CET 2015


Hello Daniel, 
Here debug of the notify which failing. Look like transaction miss match 

http://fpaste.org/196896/61168591/ 

Slava. 



From: "Daniel-Constantin Mierla" <miconda at gmail.com> 
To: "Slava Bendersky" <volga629 at networklab.ca>, "sr-users" <sr-users at lists.sip-router.org> 
Sent: Wednesday, March 11, 2015 5:44:05 PM 
Subject: Re: [SR-Users] kamailio asterisk NOTIFY 

Hello, 

it doesn't matter if there is a mix of transports. If the UA is mirroring the Record-Route headers in the response to the NOTIFY, it should work fine. 

Cheers, 
Daniel 

On 11/03/15 21:40, Slava Bendersky wrote: 



Hello Daniel, 
Is this matter that UDP and TCP transport in mix ? 

Slava. 



From: "Slava Bendersky" <volga629 at networklab.ca> 
To: miconda at gmail.com 
Cc: "sr-users" <sr-users at lists.sip-router.org> 
Sent: Wednesday, March 11, 2015 4:21:39 PM 
Subject: Re: [SR-Users] kamailio asterisk NOTIFY 

Hello Daniel, 
I have record route in WITHINDLG for NOTIFY, but it not helped behaviour is the same it loosing route for NOTIFY. 


Slava. 


From: "Daniel-Constantin Mierla" <miconda at gmail.com> 
To: "Slava Bendersky" <volga629 at networklab.ca> , "sr-users" <sr-users at lists.sip-router.org> 
Sent: Wednesday, March 11, 2015 2:14:02 PM 
Subject: Re: [SR-Users] kamailio asterisk NOTIFY 

Hello, 

you have to do record_route() for all NOTIFY requests -- there are new specs requiring that (RFC 6665) and perhaps asterisk is following them. 

If you look in the default kamailio.cfg for v4.2, inside route[WITHINDLG], then you will see how it is done. 

Cheers, 
Daniel 

On 11/03/15 14:22, Slava Bendersky wrote: 

BQ_BEGIN

Hello Daniel, 
Here fresh paste 

http://fpaste.org/196616/42608006/ 

I see proper routing headers on SUBSCRIBE, but then NOTIFY loose it. 

Slava. 


From: "Daniel-Constantin Mierla" <miconda at gmail.com> 
To: "sr-users" <sr-users at lists.sip-router.org> 
Sent: Tuesday, March 10, 2015 5:31:51 PM 
Subject: Re: [SR-Users] kamailio asterisk NOTIFY 

Hello, 

fpaste link doesn't show anything. 

Can you check if the NOTIFY coming to Kamailio has two Route headers? 

Cheers, 
Daniel 

On 10/03/15 18:44, Slava Bendersky wrote: 

BQ_BEGIN

Hello Everyone, 
Having issue with NOTIFY, is not forwarded to client properly. 

asterisk ---> private kamailio public ----> soft client 


http://fpaste.org/196257/99948714/ 

I see kamailio trying connect always with private IP to the client when NOTIFY is come is in. Is this something to do with 
rr_advertise_address ? 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) ERROR: <core> [tcp_main.c:4338]: tcpconn_main_timeout(): connect 192.168.88.246:5064 failed (timeout) 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [tcp_main.c:4362]: tcpconn_main_timeout(): tcp_main: timeout for 0x7fbbb64e2800 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9dbf00, 33, -1, 0x10) fd_no=24 called 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [tcp_main.c:4320]: tcpconn_main_timeout(): tcp_main: entering timer for 0x7fbbb64eb6c0 (ticks=839577436, timeout=839634956 (3595 s), wr_timeout=839577436 (0 s)), write queue: 798 bytes 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) ERROR: <core> [tcp_main.c:4338]: tcpconn_main_timeout(): connect 192.168.88.246:5066 failed (timeout) 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [tcp_main.c:4362]: tcpconn_main_timeout(): tcp_main: timeout for 0x7fbbb64eb6c0 
Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9dbf00, 34, -1, 0x10) fd_no=23 called 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1294]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=408 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1812]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: <core> [mem/shm_mem.c:111]: _shm_resize(): WARNING:vqm_resize: resize(0) called 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1294]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=408 
Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1812]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 

I have in configuration in WITHINDLG 

if (is_method("NOTIFY")) { 
record_route(); 
} 

and in NATDETECT 

if(is_method("INVITE|SUBSCRIBE|UPDATE|NOTIFY")) { 
set_contact_alias(); 
} 

Slava. 


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users at lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 



-- 
Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com 

_______________________________________________ 
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list 
sr-users at lists.sip-router.org 
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 

BQ_END

-- 
Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com 


_______________________________________________ 
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list 
sr-users at lists.sip-router.org 
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 

BQ_END

-- 
Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20150311/45f4c5f9/attachment.html>


More information about the sr-users mailing list