05-28-2015, 12:07 AM
Hey Guys,
We recently purchased some T27 phones that run a new firmware, 45.80.0.25. The BLF lights do not work. I've confirmed positive SUBSCRIBEs, and NOTIFYs being sent to the phones, to which the phone responds with a 200 OK, but no light.
I believe this may be with the dialog-info, perhaps it does not like/recognize the state? Firmware V72 works fine on the T26/28, etc. I was hoping to have a tech take a look at this. I can get you pcaps from the router and phone alike if required. Below is a snippet of a NOTIFY sent by my server that did not illuminate the BLF. I've tried multiple BLF modes (0,1,2, etc) not no avail. Thoughts?
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
[tos 0xb8]
16:11:11.209048 kam001.REMOVED.5060 > 10.30.10.111.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
NOTIFY sip:sipoff_f105@10.30.10.111:5060 SIP/2.0
Via: SIP/2.0/UDP 162.252.248.41;branch=z9hG4bK1a3b.c4b87c05000000000000000000000000.0
Record-Route: <sip:sipoff_f105@162.252.248.41;lr>
From: <sip:*31@off.jh.atlas.wlcomm.net>;tag=f60b39ccd0c69fb84f0c4ccb3f5af2c8-cdc2
To: <sip:sipoff_f105@off.jh.atlas.wlcomm.net>;tag=1295495930
Call-ID: 0_4166604576@10.30.10.111
CSeq: 2 NOTIFY
Contact: <sip:162.252.248.41:5060;transport=udp>
Max-forwards: 70
Event: dialog
Subscription-state: active;expires=1800
Content-Type: application/dialog-info+xml
Content-Length: 688
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="2" state="full" entity="sip:*31@off.jh.atlas.wlcomm.net">
<dialog id="0d491fa45a71934a39f23aa17f7d84e2" call-id="0d491fa45a71934a39f23aa17f7d84e2" local-tag="K34XgNcB5Bape" remote-tag="gK0eb26726" direction="recipient">
<state>confirmed</state>
<local>
<identity display="*31">sip:*31@off.jh.atlas.wlcomm.net</identity>
<target uri="sip:*31@off.jh.atlas.wlcomm.net"/>
</local>
<remote>
<identity display="+16468541510">sip:+16468541510@72.15.219.140</identity>
<target uri="sip:+16468541510@72.15.219.140"/>
</remote>
</dialog>
</dialog-info>
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
[tos 0xb8]
16:11:11.215871 10.30.10.111.5060 > kam001.REMOVED.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 162.252.248.41;branch=z9hG4bK1a3b.c4b87c05000000000000000000000000.0
From: <sip:*31@off.jh.atlas.wlcomm.net>;tag=f60b39ccd0c69fb84f0c4ccb3f5af2c8-cdc2
To: <sip:sipoff_f105@off.jh.atlas.wlcomm.net>;tag=1295495930
Call-ID: 0_4166604576@10.30.10.111
CSeq: 2 NOTIFY
User-Agent: Yealink SIP-T27P 45.80.0.25
Content-Length: 0
We recently purchased some T27 phones that run a new firmware, 45.80.0.25. The BLF lights do not work. I've confirmed positive SUBSCRIBEs, and NOTIFYs being sent to the phones, to which the phone responds with a 200 OK, but no light.
I believe this may be with the dialog-info, perhaps it does not like/recognize the state? Firmware V72 works fine on the T26/28, etc. I was hoping to have a tech take a look at this. I can get you pcaps from the router and phone alike if required. Below is a snippet of a NOTIFY sent by my server that did not illuminate the BLF. I've tried multiple BLF modes (0,1,2, etc) not no avail. Thoughts?
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
[tos 0xb8]
16:11:11.209048 kam001.REMOVED.5060 > 10.30.10.111.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
NOTIFY sip:sipoff_f105@10.30.10.111:5060 SIP/2.0
Via: SIP/2.0/UDP 162.252.248.41;branch=z9hG4bK1a3b.c4b87c05000000000000000000000000.0
Record-Route: <sip:sipoff_f105@162.252.248.41;lr>
From: <sip:*31@off.jh.atlas.wlcomm.net>;tag=f60b39ccd0c69fb84f0c4ccb3f5af2c8-cdc2
To: <sip:sipoff_f105@off.jh.atlas.wlcomm.net>;tag=1295495930
Call-ID: 0_4166604576@10.30.10.111
CSeq: 2 NOTIFY
Contact: <sip:162.252.248.41:5060;transport=udp>
Max-forwards: 70
Event: dialog
Subscription-state: active;expires=1800
Content-Type: application/dialog-info+xml
Content-Length: 688
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="2" state="full" entity="sip:*31@off.jh.atlas.wlcomm.net">
<dialog id="0d491fa45a71934a39f23aa17f7d84e2" call-id="0d491fa45a71934a39f23aa17f7d84e2" local-tag="K34XgNcB5Bape" remote-tag="gK0eb26726" direction="recipient">
<state>confirmed</state>
<local>
<identity display="*31">sip:*31@off.jh.atlas.wlcomm.net</identity>
<target uri="sip:*31@off.jh.atlas.wlcomm.net"/>
</local>
<remote>
<identity display="+16468541510">sip:+16468541510@72.15.219.140</identity>
<target uri="sip:+16468541510@72.15.219.140"/>
</remote>
</dialog>
</dialog-info>
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
[tos 0xb8]
16:11:11.215871 10.30.10.111.5060 > kam001.REMOVED.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 162.252.248.41;branch=z9hG4bK1a3b.c4b87c05000000000000000000000000.0
From: <sip:*31@off.jh.atlas.wlcomm.net>;tag=f60b39ccd0c69fb84f0c4ccb3f5af2c8-cdc2
To: <sip:sipoff_f105@off.jh.atlas.wlcomm.net>;tag=1295495930
Call-ID: 0_4166604576@10.30.10.111
CSeq: 2 NOTIFY
User-Agent: Yealink SIP-T27P 45.80.0.25
Content-Length: 0