- Joined
- Aug 29, 2017
- Messages
- 28
- Reaction score
- 4
Hi all,
we have some 2N IP Verso intercoms at several doors and since the update to 3CX version 18, these intercoms cannot call any T40G phones. This is a really strange behavior, other phones can be called without any problems, only the T40G is not working. The call never reaches the T40G and under "Active calls" in the Management console, I just see the stauts "Initiating" for the call.
All devices are on the latest firmware. I performed tests with the latest 3CX version for the T40G (T40G-76.84.0.95) and also the latest from Yealink site (T40G-76.84.0.125). We normally use customized templates but for sure we applied the latest 3CX template without any change.
I created a log on the IP Verso and found these lines:
Cheers,
Timo
we have some 2N IP Verso intercoms at several doors and since the update to 3CX version 18, these intercoms cannot call any T40G phones. This is a really strange behavior, other phones can be called without any problems, only the T40G is not working. The call never reaches the T40G and under "Active calls" in the Management console, I just see the stauts "Initiating" for the call.
All devices are on the latest firmware. I performed tests with the latest 3CX version for the T40G (T40G-76.84.0.95) and also the latest from Yealink site (T40G-76.84.0.125). We normally use customized templates but for sure we applied the latest 3CX template without any change.
I created a log on the IP Verso and found these lines:
Has anybody seen similar problems with 2N and Yealink devices?<135>Jan 5 14:13:44.521 SST: sipstack_handle_sip_event(): SIP1 SIP_CALL_REQUESTFAILURE (cid = 43)
<135>Jan 5 14:13:44.521 SIP: _sipstack_on_call_failure(): call failed (sipcall = 85516780, status code = 407)
Cheers,
Timo