On Monday, March 23, 2015 11:18:01 PM Daniel-Constantin Mierla wrote: > Hello, > > not sure you mean transaction as used inside kamailio (tm module), but a SIP > transaction doesn't have anything to do with routing. Kamailio will be able > to route requests/replies even when not creating transactions (i.e., when > it is stateless forwarding). > > It looks like you get the sip packets from the asterisk box. Use ngrep on > kamailio server to see what happens there, like: > > ngrep -d any -qt -W byline port 5060 or port 5062 > > You will see if the packets get to kamailio and if they are attempted to be > sent further. > > Cheers, > Daniel
This may or may not be related, but I am also having issues with NOTIFY for MWI from Asterisk. In my case I am using the TOPOH module and it appears Asterisk may be truncating the Request-URI on NOTIFYs *after* the 1st one. Where the 1st one is if a user gets NOTIFY immediately upon the first SUBSCRIBE, such as when there is already a VM in their mailbox. https://issues.asterisk.org/jira/browse/ASTERISK-24877 -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
