Hi partners.
My hardware information
Linux 2.6.32-642.6.2.el6.x86_64 on x86_64
Processor information Intel(R) Xeon(R) CPU E5504 @ 2.00GHz, 4 cores
4 GB RAM
Asterisk 13.17.1
FreePBX 13.0.192.18
I'm trying that the voice mail lamp in the phone turn on when the user have a new voice mail... but I want that using chan_sip. with chan_pjsip work fine the lamp, but I dont want use pjsip because the tech is not mature and have issues.
this is the information that I discovery on internet about the MWI
SIP MWI
Message Waiting notifications in SIP are done with the notify method
NOTIFY
During the subscription period, the Gateway may, from time to time, send a spontaneous NOTIFY request to the entity indicated in the Contact: header of the "opening" SUBSCRIBE request. Normally this will happen as a result of any change in the status of the service session for which the Requestor has subscribed.
MY ISSUES
The issue that I fund with this phone, is the phone do not understand the event part in the SIP NOTIFY when I use chan_sip. but if I use chan_pjsip work fine. so my idea is to edit the NOTIFY massage on chan_sip to look similar to the chan_sip but I'm not sure how to that if some can give me any suggestion
below you can see the differents NOTIFY message.
THIS THE PJSIP
NOTIFY sip:200@192.168.2.99:40673;transport=TCP SIP/2.0
Via: SIP/2.0/TCP 192.168.2.97:5062;rport;branch=z9hG4bKPj77147dc6-4522-4892-b73c-7ee29566010a;alias
From: ;tag=92c200bd-6d04-4efc-9070-03e5bf5a2eae
To: ;tag=59c94ef423b8ef3d3f426p4n3a6t4a12483w3m3w2g1g1e4f2340_F200192.168.2.99
Contact:
Call-ID: 3_59c94ef4-7ec396bf4062ewbp6b1d4s6m70231q6o4s434f5k_S200192.168.2.99
CSeq: 27679 NOTIFY
Event: message-summary
Subscription-State: terminated
Allow-Events: message-summary, presence, dialog, refer
Max-Forwards: 70
User-Agent: FPBX-13.0.192.18(13.17.0)
Content-Type: application/simple-message-summary
Content-Length: 48
Messages-Waiting: no
Voice-Message: 0/0 (0/0)
THIS THE RESPONSE FROM THE PHONE
SIP/2.0 200 OK
From: ;tag=92c200bd-6d04-4efc-9070-03e5bf5a2eae
To: ;tag=59c94ef423b8ef3d3f426p4n3a6t4a12483w3m3w2g1g1e4f2340_F200192.168.2.99
Call-ID: 3_59c94ef4-7ec396bf4062ewbp6b1d4s6m70231q6o4s434f5k_S200192.168.2.99
CSeq: 27679 NOTIFY
Via: SIP/2.0/TCP 192.168.2.97:5062;alias;branch=z9hG4bKPj77147dc6-4522-4892-b73c-7ee29566010a
User-Agent: Avaya one-X Deskphone 7.0.1.4.6 (6)
Content-Length: 0
THIS IS THE SIP
NOTIFY sip:201@192.168.2.100:47384;transport=tcp;avaya-sc-enabled SIP/2.0
Via: SIP/2.0/TCP 192.168.2.97:5060;branch=z9hG4bK3ac758d3
Max-Forwards: 70
From: "Unknown" ;tag=as32beee25
To:
Contact:
Call-ID: 72b56fdb0d238ee57eeaf345215caf6c@192.168.2.97:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-13.0.192.18(13.17.0)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 101
Messages-Waiting: no
Message-Account: sip:*97@192.168.2.97;transport=TCP
Voice-Message: 0/0 (0/0)
THIS THE RESPONSE FROM THE PHONE
SIP/2.0 400 Bad Request (Unknown Subscription State)
From: "Unknown" ;tag=as32beee25
To:
Call-ID: 72b56fdb0d238ee57eeaf345215caf6c@192.168.2.97:5060
CSeq: 102 NOTIFY
Via: SIP/2.0/TCP 192.168.2.97:5060;branch=z9hG4bK3ac758d3
User-Agent: Avaya one-X Deskphone 7.0.1.4.6 (6)
Content-Length: 0
The difference between both massage are
the PJSIP send the user in the FROM field
the SIP send UNKNOW in the FROM Field
PJSIP has Subscription-State field, sip dot not have this
PJSIP has more options in the field of Allow-Events