PJSIP Qualify

Home » Asterisk Users » PJSIP Qualify
Asterisk Users 2 Comments

I am currently not using qualify, but it seems like a nice way to know if the phones are online. I attempted to set it up, but am running into a 404
on the subscription.

1. From the manager, Action: PJSIPNotify (with an endpoint). This caused the following OPTIONS packet to be sent to the phone.

OPTIONS sip:64167f3a7955@192.168.2.206 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.22:5060
;rport;branch=z9hG4bKPj232f200b-90a0-4c2b-8171-164f9961175d From:
Contact:
Call-ID: 68897833-b4d3-4a75-9ad1-939b752d5a5e CSeq: 47099 OPTIONS
Max-Forwards: 70
User-Agent: Asterisk PBX 16.1.0
Content-Length: 0

2. The phone acknowledges the OPTIONS

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.22:5060
;rport;branch=z9hG4bKPj232f200b-90a0-4c2b-8171-164f9961175d From: ;tag

2 thoughts on - PJSIP Qualify

  • The OPTIONS and the SUBSCRIBE are unrelated. If an OPTIONS goes out and gets a response, then it’s working.

    The SUBSCRIBE is the phone attempting to subscribe to receive MWI information. There are two ways to do this: unsolicited – which is Asterisk sending a NOTIFY without the phone having asked for it, and solicited which is this case where the phone does a SUBSCRIBE to receive it. To allow this case the mailboxes have to be configured on the AOR instead of the endpoint.


    Joshua C. Colp Digium – A Sangoma Company | Senior Software Developer
    445 Jan Davis Drive NW – Huntsville, AL 35806 – US
    Check us out at: http://www.digium.com & http://www.asterisk.org

  • Please ignore my previous email. Qualify is now working well. The packets that were misleading me were related to MWI subscription, and not the result of Qualify (OPTIONS).. Sorry for any confusion.