BLF(Broadworks) Icons Issue on T48G

[hari908]

I have created the BLF URI in broadsoft r18/r19/r20 server as hari123

From phone's web UI
Go to page
Account ->Advanced
Set BLF List URI to hari123

I am able to see the BLF lines on the phone.
But when i am placing calls to BLF lines from other phone, the BLF line icon showing ringing even after the answering the call. This remains in ringing state even after ending the call on BLF line. The icons get cleared after leaving the phone for 10-15min.

Is there any other configuration that needs to be done?
The same works perfectly on Polycom phones.

Thanks in advance

[James_Yealink]

Hi Hari908,

What's your phone firmware?
The BLF status depends on the NOTIFY message sent by sip server. If phone receive a NOTIFY message which tell phone change to BLF status to idle, it shouldn't remain in ringing state.
Is the T48G in a same network to Polycom phones?

If possible can you get a pcap file and level 6 syslog in the process? We will check whether phone receive a Notify message when ending a call.

For how to get a pcap file and syslog:
http://forum.yealink.com/forum/showthread.php?tid=1319

Regards,
James

[hari908]

Please find my answers inline. Attached the syslog, pcap and config in yealink_TP48G.zip

Scenario Tested:
1. Yealink(1647) monitors BLF Line 1648.
2. 1649 calls 1648. 1648 answers and establishes call with 1649.
3. After few seconds, 1649 ends the call.

(09-10-2014 04:54 PM)Yealink_James Wrote:  Hi Hari908,

What's your phone firmware?
>> 35.72.193.10

The BLF status depends on the NOTIFY message sent by sip server. If phone receive a NOTIFY message which tell phone change to BLF status to idle, it shouldn't remain in ringing state.
Is the T48G in a same network to Polycom phones?
>>> Both are connected to the same POE switch.

If possible can you get a pcap file and level 6 syslog in the process? We will check whether phone receive a Notify message when ending a call.

>> Attached the syslog, pcap and config in yealink_TP48G.zip

For how to get a pcap file and syslog:
http://forum.yealink.com/forum/showthread.php?tid=1319

Regards,
James

[James_Yealink]

Thanks for these information, I have transferred them to our R&D and they will have an analysis.

May I confirm these two points:

1.Have you created a device type of T48 and created a device profile for this T48 based on the T48 type?
2.How many phones are experience the problem now?


Regards,
James

[hari908]

Please find my answers inline.

(09-16-2014 05:24 PM)Yealink_James Wrote:  Thanks for these information, I have transferred them to our R&D and they will have an analysis.


May I confirm these two points:

1.Have you created a device type of T48 and created a device profile for this T48 based on the T48 type?
>> Yes i have created T42G device type. T48G CPE kit downloaded from your website is throwing error when imported. Attached is the screenshot(CPE_KIT_Import_Error.png).

2.How many phones are experience the problem now?
Currently i have 2 T48G phones and both are giving the same problem


Regards,
James

[hari908]

James,

Request you to provide update on this.

(09-16-2014 08:40 PM)hari908 Wrote:  Please find my answers inline.

(09-16-2014 05:24 PM)Yealink_James Wrote:  Thanks for these information, I have transferred them to our R&D and they will have an analysis.


May I confirm these two points:

1.Have you created a device type of T48 and created a device profile for this T48 based on the T48 type?
>> Yes i have created T42G device type. T48G CPE kit downloaded from your website is throwing error when imported. Attached is the screenshot(CPE_KIT_Import_Error.png).

2.How many phones are experience the problem now?
Currently i have 2 T48G phones and both are giving the same problem


Regards,
James

[James_Yealink]

Hi Hari,

According to our R&D, it seems that the problem is related to the port Broadsoft send.
Can you please try adding this parameter by autoprovision and check again.

sip.send_response_by_request=1

Autoprovision guide:
http://www.yealink.com/Upload/T4X/201412..._V72_2.pdf

Regards,
James

[James_Yealink]

If the problem is not solved, please send a new pcap/syslog/config.bin.

Thanks

[James_Yealink]

Sorry Hari,
I send a wrong parameter, the value should be 0.

sip.send_response_by_request= 0

Please try this autoprovision parameter.

Regards,
James

[hari908]

James,

I am facing the same problem even after setting sip.send_response_by_request= 0.

Attached are the pcap, config and logs as attachment Logs_6th_Oct.zip.

(09-30-2014 01:30 PM)Yealink_James Wrote:  Sorry Hari,
I send a wrong parameter, the value should be 0.

sip.send_response_by_request= 0

Please try this autoprovision parameter.

Regards,
James