Hi, I'm trying to connect the PJSUA sample app to a public asterisk box. I am behind a cisco PIX firewall. I can make outbound calls fine, but on all inbound calls, asterisk thinks that my line is busy. I am receiving NOTIFY packets from asterisk, however I see the following message a lot in the console output: 11:09:02.156 sip_endpoint.c Message Request msg NOTIFY/cseq=102 (rdata00BE5EAC) from 64.209.211.3:5060 was dropped/unhandled by any modules So it seems as though the app isn't responding to NOTIFY messages, so asterisk thinks I am offline. Is there a way to fix this? Thanks. -- James

On 3/21/08, James Lamanna <jlamanna@gmail.com> wrote: > Hi, > I'm trying to connect the PJSUA sample app to a public asterisk box. > I am behind a cisco PIX firewall. > I can make outbound calls fine, but on all inbound calls, asterisk > thinks that my line is busy. > > I am receiving NOTIFY packets from asterisk, however I see the > following message a lot in the console output: > > 11:09:02.156 sip_endpoint.c Message Request msg NOTIFY/cseq=102 (rdata00BE5EAC) > from 64.209.211.3:5060 was dropped/unhandled by any modules > > So it seems as though the app isn't responding to NOTIFY messages, so > asterisk thinks I am offline. > Is there a way to fix this? pjsua doesn't handle unsolicited NOTIFY's (and personally I think it's bad that the server does this when client doesn't indicate support for this extension). But if your application wants to handle this, it's very easy to implement. Just write a pjsip module, watch for incoming NOTIFY in your on_rx_request() callback, sends 200/OK if so, and register the pjsip module to pjsip endpoint. For more info about pjsip module please see the Developer's Guide PDF. Cheers Benny > Thanks. > > -- James

>On 3/21/08, James Lamanna <jlamanna@gmail.com> wrote: >> Hi, >> I'm trying to connect the PJSUA sample app to a public asterisk box. >> I am behind a cisco PIX firewall. >> I can make outbound calls fine, but on all inbound calls, asterisk >> thinks that my line is busy. >> >> I am receiving NOTIFY packets from asterisk, however I see the >> following message a lot in the console output: >> >> 11:09:02.156 sip_endpoint.c Message Request msg NOTIFY/cseq=102 (rdata00BE5EAC) >> from 64.209.211.3:5060 was dropped/unhandled by any modules >> >> So it seems as though the app isn't responding to NOTIFY messages, so >> asterisk thinks I am offline. >> Is there a way to fix this? > pjsua doesn't handle unsolicited NOTIFY's (and personally I think it's > bad that the server does this when client doesn't indicate support for > this extension). > > But if your application wants to handle this, it's very easy to > implement. Just write a pjsip module, watch for incoming NOTIFY in > your on_rx_request() callback, sends 200/OK if so, and register the > pjsip module to pjsip endpoint. For more info about pjsip module > please see the Developer's Guide PDF. Thanks for the reply. Am I correct that this would make asterisk think that my extension is always busy? That's the real problem I'm trying to fix because it means that all incoming calls go directly to voicemail. Please CC me directly for I only get list digests. Thanks. -- James

Check you asterisk configuration for the qualify option. Qualify is the responsible for sending those "keep alive" messages if I am correct. By setting qualify=no on the peer, you will stop receiving the NOTIFY msgs. I am not sure what would be the proper response to those transactions to make the qualify option work properly. Thanks, Mesquita On Sat, 2008-03-22 at 10:00 -0700, James Lamanna wrote: > >On 3/21/08, James Lamanna <jlamanna@gmail.com> wrote: > >> Hi, > >> I'm trying to connect the PJSUA sample app to a public asterisk box. > >> I am behind a cisco PIX firewall. > >> I can make outbound calls fine, but on all inbound calls, asterisk > >> thinks that my line is busy. > >> > >> I am receiving NOTIFY packets from asterisk, however I see the > >> following message a lot in the console output: > >> > >> 11:09:02.156 sip_endpoint.c Message Request msg NOTIFY/cseq=102 > (rdata00BE5EAC) > >> from 64.209.211.3:5060 was dropped/unhandled by any modules > >> > >> So it seems as though the app isn't responding to NOTIFY messages, so > >> asterisk thinks I am offline. > >> Is there a way to fix this? > > > pjsua doesn't handle unsolicited NOTIFY's (and personally I think it's > > bad that the server does this when client doesn't indicate support for > > this extension). > > > > But if your application wants to handle this, it's very easy to > > implement. Just write a pjsip module, watch for incoming NOTIFY in > > your on_rx_request() callback, sends 200/OK if so, and register the > > pjsip module to pjsip endpoint. For more info about pjsip module > > please see the Developer's Guide PDF. > > Thanks for the reply. > Am I correct that this would make asterisk think that my extension is > always busy? > That's the real problem I'm trying to fix because it means that all > incoming calls go directly to voicemail. > > Please CC me directly for I only get list digests. > > Thanks. > > -- James > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

Yes, but since I'm behind NAT, those keep alives I believe are responsible for keeping the hole through the firewall. -- James On Sat, Mar 22, 2008 at 11:42 AM, João Mesquita <jmesquita@contactnet.com.br> wrote: > Check you asterisk configuration for the qualify option. > > Qualify is the responsible for sending those "keep alive" messages if I > am correct. > > By setting qualify=no on the peer, you will stop receiving the NOTIFY > msgs. > > I am not sure what would be the proper response to those transactions to > make the qualify option work properly. > > Thanks, > > Mesquita > > > > On Sat, 2008-03-22 at 10:00 -0700, James Lamanna wrote: > > >On 3/21/08, James Lamanna <jlamanna@gmail.com> wrote: > > >> Hi, > > >> I'm trying to connect the PJSUA sample app to a public asterisk box. > > >> I am behind a cisco PIX firewall. > > >> I can make outbound calls fine, but on all inbound calls, asterisk > > >> thinks that my line is busy. > > >> > > >> I am receiving NOTIFY packets from asterisk, however I see the > > >> following message a lot in the console output: > > >> > > >> 11:09:02.156 sip_endpoint.c Message Request msg NOTIFY/cseq=102 > > (rdata00BE5EAC) > > >> from 64.209.211.3:5060 was dropped/unhandled by any modules > > >> > > >> So it seems as though the app isn't responding to NOTIFY messages, so > > >> asterisk thinks I am offline. > > >> Is there a way to fix this? > > > > > pjsua doesn't handle unsolicited NOTIFY's (and personally I think it's > > > bad that the server does this when client doesn't indicate support for > > > this extension). > > > > > > But if your application wants to handle this, it's very easy to > > > implement. Just write a pjsip module, watch for incoming NOTIFY in > > > your on_rx_request() callback, sends 200/OK if so, and register the > > > pjsip module to pjsip endpoint. For more info about pjsip module > > > please see the Developer's Guide PDF. > > > > Thanks for the reply. > > Am I correct that this would make asterisk think that my extension is > > always busy? > > That's the real problem I'm trying to fix because it means that all > > incoming calls go directly to voicemail. > > > > Please CC me directly for I only get list digests. > > > > Thanks. > > > > -- James > > > > _______________________________________________ > > Visit our blog: http://blog.pjsip.org > > > > pjsip mailing list > > pjsip@lists.pjsip.org > > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >

On Sat, Mar 22, 2008 at 7:19 PM, James Lamanna <jlamanna@gmail.com> wrote: > Yes, but since I'm behind NAT, those keep alives I believe are > responsible for keeping the hole through the firewall. > IMO it should be client's responsibility to do keep-alive, and that's just what PJSIP does. So there's no need to enable this on your server. Cheers, -benny