T46G Firmware 28.80.0.60 disables the intercom auto-answer function

[KenDoerksen]

I have tested on 4 different phones now all hardware version 28.2.0.128.0.0.0. When using the intercom between the phones on firmware version 28.80.0.60 the phones just ring. I downgraded the phones to firmware version 28.73.0.50 and they all auto-answer the incoming intercom as expected again.

Any time table for this to get fixed?

[Karl_Yealink]

Hi,

You can try to configure the setting from web interface(Features->Intercom->Intercom Barge).

[KenDoerksen]

(12-02-2015 05:05 PM)Yealink_Karl Wrote:  Hi,

You can try to configure the setting from web interface(Features->Intercom->Intercom Barge).

No one is on the phone. We are setting them up in our office so it isn't a barge issue. This is a simple auto answer issue. There is something in the new firmware that is buggy and causing it to not work correctly. We are currently trying to use the FTP configuration to downgrade all of our client phones to the version right before 80.0.60 so that the intercom works.

[Karl_Yealink]

Hi,

I had tested here, and the intercom between T46G on version 28.80.0.60 is OK.
So would you please help us to get the pcap/syslog/config.bin for us, we can check something from them.
You can get more info from the link: http://forum.yealink.com/forum/showthread.php?tid=1319

Please help us to get some info below.
1. Will the intercom work between T46G on version 28.80.0.60 and 28.73.0.50?
2. How many phones do you have?
3. What PBX server of you?

[KenDoerksen]

(12-03-2015 04:15 PM)Yealink_Karl Wrote:  Hi,

I had tested here, and the intercom between T46G on version 28.80.0.60 is OK.
So would you please help us to get the pcap/syslog/config.bin for us, we can check something from them.
You can get more info from the link: http://forum.yealink.com/forum/showthread.php?tid=1319

Please help us to get some info below.
1. Will the intercom work between T46G on version 28.80.0.60 and 28.73.0.50?
2. How many phones do you have?
3. What PBX server of you?

1.The intercom works between the two firmware versions. Sending the intercom command from a 28.80 to a 28.73 the intercom tones and then picks up. Sending the intercom command from a 28.73 to a 28.80, the phone rings until it is answered.

2. We have a total of 16 phones 13 T46Gs 2 T48Gs (same problem with newest firmware) and 1 Conference phone (haven't tested to this phone as it's not needed).

3. We are using Core Dial for a hosted PBX server.

Unfortunately I am unable to get the log file information from any phones with the 28.80 as we had to do the install today and downgrade all phones so they work correctly.

[c.holloway]

(12-04-2015 01:53 AM)KenDoerksen Wrote:  

(12-03-2015 04:15 PM)Yealink_Karl Wrote:  Hi,

I had tested here, and the intercom between T46G on version 28.80.0.60 is OK.
So would you please help us to get the pcap/syslog/config.bin for us, we can check something from them.
You can get more info from the link: http://forum.yealink.com/forum/showthread.php?tid=1319

Please help us to get some info below.
1. Will the intercom work between T46G on version 28.80.0.60 and 28.73.0.50?
2. How many phones do you have?
3. What PBX server of you?

1.The intercom works between the two firmware versions. Sending the intercom command from a 28.80 to a 28.73 the intercom tones and then picks up. Sending the intercom command from a 28.73 to a 28.80, the phone rings until it is answered.

2. We have a total of 16 phones 13 T46Gs 2 T48Gs (same problem with newest firmware) and 1 Conference phone (haven't tested to this phone as it's not needed).

3. We are using Core Dial for a hosted PBX server.

Unfortunately I am unable to get the log file information from any phones with the 28.80 as we had to do the install today and downgrade all phones so they work correctly.

I am having a similar issue. I have 10 phones all together. 8 T42s and 2 T46s. The T42s are on firmware version 29.80.0.70 and the T46s are on 28.73.0.50. The PBX is 3CX version 14.

Intercoming does not work in either direction. I have made sure it is enabled on both phones. I took a capture from both phones involved in my test call. This was a call from a T42 to a T46. The capture is labeled with the firmware load and phone type. The config.bin is labeled with the phone type. Please let me know if I can get you any more information.

[Karl_Yealink]

Hi,

I had tested here, and T42G and T46G with your version all can work normally.
From the PCAP, I find the invite message don't contain the "intercom=ture". I think you don't capture the intercom process.

Please check do you enable the Accept Intercom(web interface->featuers->intercom) firstly.
Then check whether the server support the function.

If possible, please get the PCAP file again, note that press the start button then repeat the issue, and export the PCAP file.

[c.holloway]

(12-07-2015 11:55 PM)Yealink_Karl Wrote:  Hi,

I had tested here, and T42G and T46G with your version all can work normally.
From the PCAP, I find the invite message don't contain the "intercom=ture". I think you don't capture the intercom process.

Please check do you enable the Accept Intercom(web interface->featuers->intercom) firstly.
Then check whether the server support the function.

If possible, please get the PCAP file again, note that press the start button then repeat the issue, and export the PCAP file.

Karl,

I found the issue. I didn't have "Allow Intercom" checked under the Rights tab of the extension in 3CX. Thank you for your time.

[dew3flr]

(12-02-2015 08:10 AM)KenDoerksen Wrote:  I have tested on 4 different phones now all hardware version 28.2.0.128.0.0.0. When using the intercom between the phones on firmware version 28.80.0.60 the phones just ring. I downgraded the phones to firmware version 28.73.0.50 and they all auto-answer the incoming intercom as expected again.

Any time table for this to get fixed?

where did you set the intercom auto-answer in 28.73.0.50 ? Only see general auto answer - which auto answers all calls. No choices in Features/Intercom ?

[Renusa-Bryan]

Not sure about the functioning in this version, but 28.80.0.70 is available. Maybe it got fixed?