yealink T54W and incompatible destination dialing

wa4zlw

wa4zlw

Member
Jun 7, 2019
142
2
18
70
Blandon, PA
www.myinternetsupport.com
Hi there!

Trying to turn up a customer and they have these devices. Inbound works fine. Dialing out, extension or a number, I get that error. I have checked and two Codecs match PCMA and PCMU. I also reduced the number of codecs on the device. Google doesnt come up with much except codec issues.

If someone can point me in the right direction, I would be greatly appreciated. I've changed the real IPs and FQDNs.

Thanks leon

Here's a snippet from the log yesterday:

2025-06-12 15:39:32.301132 97.83% [DEBUG] sofia.c:10554 verifying acl "providers" for ip/port 1.2.3.4:0.
2025-06-12 15:39:32.301132 97.83% [WARNING] sofia_reg.c:1842 SIP auth challenge (INVITE) on sofia profile 'internal' for [1010@mypbx.com] from ip 1.2.3.4
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.301132 97.83% [DEBUG] switch_core_state_machine.c:600 (sofia/internal/1001@mypbx.com:5060) State NEW
2025-06-12 15:39:32.301132 97.83% [DEBUG] sofia.c:2419 detaching session 14d067a6-03a2-4569-b805-28c44bbf6350
2025-06-12 15:39:32.421152 97.83% [DEBUG] sofia.c:2532 Re-attaching to session 14d067a6-03a2-4569-b805-28c44bbf6350
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [INFO] sofia.c:10460 sofia/internal/1001@mypbx.com:5060 receiving invite from 1.2.3.4:10624 version: 1.10.12-release git d8481a9 2025-01-13 17:41:43Z 64bit call-id: 1_1147233283@10.1.10.138
2025-06-12 15:39:32.421152 97.83% [DEBUG] sofia.c:10554 verifying acl "providers" for ip/port 1.2.3.4:0.
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] sofia.c:11675 Setting NAT mode based on via received
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] sofia.c:7493 Channel sofia/internal/1001@mypbx.com:5060 entering state [received][100]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] sofia.c:7503 Remote SDP:
14d067a6-03a2-4569-b805-28c44bbf6350 v=0
14d067a6-03a2-4569-b805-28c44bbf6350 o=- 20149 20149 IN IP4 10.1.10.138
14d067a6-03a2-4569-b805-28c44bbf6350 s=SDP data
14d067a6-03a2-4569-b805-28c44bbf6350 c=IN IP4 10.1.10.138
14d067a6-03a2-4569-b805-28c44bbf6350 t=0 0
14d067a6-03a2-4569-b805-28c44bbf6350 m=audio 12702 RTP/AVP 0 18 9 8 101
14d067a6-03a2-4569-b805-28c44bbf6350 c=IN IP4 10.1.10.138
14d067a6-03a2-4569-b805-28c44bbf6350 a=rtpmap:0 PCMU/8000
14d067a6-03a2-4569-b805-28c44bbf6350 a=rtpmap:18 G729/8000
14d067a6-03a2-4569-b805-28c44bbf6350 a=fmtp:18 annexb=no
14d067a6-03a2-4569-b805-28c44bbf6350 a=rtpmap:9 G722/8000
14d067a6-03a2-4569-b805-28c44bbf6350 a=rtpmap:8 PCMA/8000
14d067a6-03a2-4569-b805-28c44bbf6350 a=rtpmap:101 telephone-event/8000
14d067a6-03a2-4569-b805-28c44bbf6350 a=fmtp:101 0-15
14d067a6-03a2-4569-b805-28c44bbf6350 a=rtcp:12703 IN IP4 10.1.10.138
14d067a6-03a2-4569-b805-28c44bbf6350 a=ptime:20
14d067a6-03a2-4569-b805-28c44bbf6350 a=candidate:472638531 1 UDP 2130706431 10.1.10.138 12702 typ host
14d067a6-03a2-4569-b805-28c44bbf6350 a=candidate:472638531 2 UDP 2130706430 10.1.10.138 12703 typ host
14d067a6-03a2-4569-b805-28c44bbf6350 a=ice-ufrag:319697fe0c03d9d95bf2e657
14d067a6-03a2-4569-b805-28c44bbf6350 a=ice-pwd:044b3c5a5efa6bc426fe917d
14d067a6-03a2-4569-b805-28c44bbf6350
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [PCMU:0:8000:20:64000:1]/[PCMU:0:8000:20:64000:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5586 Audio Codec Compare [PCMU:0:8000:20:64000:1] ++++ is saved as a match
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [PCMU:0:8000:20:64000:1]/[PCMA:8:8000:20:64000:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [PCMU:0:8000:20:64000:1]/[GSM:3:8000:20:13200:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [G729:18:8000:20:8000:1]/[PCMU:0:8000:20:64000:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [G729:18:8000:20:8000:1]/[PCMA:8:8000:20:64000:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [G729:18:8000:20:8000:1]/[GSM:3:8000:20:13200:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [G722:9:8000:20:64000:1]/[PCMU:0:8000:20:64000:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [G722:9:8000:20:64000:1]/[PCMA:8:8000:20:64000:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [G722:9:8000:20:64000:1]/[GSM:3:8000:20:13200:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [PCMA:8:8000:20:64000:1]/[PCMU:0:8000:20:64000:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [PCMA:8:8000:20:64000:1]/[PCMA:8:8000:20:64000:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5586 Audio Codec Compare [PCMA:8:8000:20:64000:1] ++++ is saved as a match
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5524 Audio Codec Compare [PCMA:8:8000:20:64000:1]/[GSM:3:8000:20:13200:1]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5436 Set telephone-event payload to 101@8000
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:3730 Set Codec sofia/internal/1001@mypbx.com:5060 PCMU/8000 20 ms 160 samples 64000 bits 1 channels
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_codec.c:132 sofia/internal/1001@mypbx.com:5060 Original read codec set to PCMU:0
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [WARNING] switch_core_media.c:4153 NO candidate ACL defined, Defaulting to wan.auto
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:4209 Save audio Candidate cid: 1 proto: UDP type: host addr: 10.1.10.138:12702
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:4209 Save audio Candidate cid: 2 proto: UDP type: host addr: 10.1.10.138:12703
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:4254 Searching for rtp candidate.
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:4254 Searching for rtcp candidate.
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:4301 Look for Relay Candidates as last resort
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:4254 Searching for rtp candidate.
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:4254 Searching for rtcp candidate.
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:4307 sofia/internal/1001@mypbx.com:5060 no suitable candidates found.
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5796 Set telephone-event payload to 101@8000
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:5854 sofia/internal/1001@mypbx.com:5060 Set 2833 dtmf send payload to 101 recv payload to 101
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [NOTICE] sofia.c:7985 Hangup sofia/internal/1001@mypbx.com:5060 [CS_NEW] [INCOMPATIBLE_DESTINATION]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] sofia.c:1527 Channel is already hungup.
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/1001@mypbx.com:5060) Running State Change CS_HANGUP (Cur 3 Tot 28382)
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:844 (sofia/internal/1001@mypbx.com:5060) Callstate Change DOWN -> HANGUP
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/1001@mypbx.com:5060) State HANGUP
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] mod_sofia.c:469 Channel sofia/internal/1001@mypbx.com:5060 hanging up, cause: INCOMPATIBLE_DESTINATION
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] mod_sofia.c:614 Responding to INVITE with: 488
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:59 sofia/internal/1001@mypbx.com:5060 Standard HANGUP, cause: INCOMPATIBLE_DESTINATION
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/1001@mypbx.com:5060) State HANGUP going to sleep
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:616 (sofia/internal/1001@mypbx.com:5060) State Change CS_HANGUP -> CS_REPORTING
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/1001@mypbx.com:5060) Running State Change CS_REPORTING (Cur 3 Tot 28382)
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/1001@mypbx.com:5060) State REPORTING
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:168 sofia/internal/1001@mypbx.com:5060 Standard REPORTING, cause: INCOMPATIBLE_DESTINATION
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/1001@mypbx.com:5060) State REPORTING going to sleep
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:607 (sofia/internal/1001@mypbx.com:5060) State Change CS_REPORTING -> CS_DESTROY
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_session.c:1748 Session 28382 (sofia/internal/1001@mypbx.com:5060) Locked, Waiting on external entities
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [NOTICE] switch_core_session.c:1766 Session 28382 (sofia/internal/1001@mypbx.com:5060) Ended
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [NOTICE] switch_core_session.c:1770 Close Channel sofia/internal/1001@mypbx.com:5060 [CS_DESTROY]
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:735 (sofia/internal/1001@mypbx.com:5060) Running State Change CS_DESTROY (Cur 2 Tot 28382)
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:745 (sofia/internal/1001@mypbx.com:5060) State DESTROY
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] mod_sofia.c:380 sofia/internal/1001@mypbx.com:5060 SOFIA DESTROY
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:175 sofia/internal/1001@mypbx.com:5060 Standard DESTROY
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_state_machine.c:745 (sofia/internal/1001@mypbx.com:5060) State DESTROY going to sleep
Click to expand...
 
Based on the logs it does smell like what google said.
14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [DEBUG] switch_core_media.c:4307 sofia/internal/1001@mypbx.com:5060 no suitable candidates found.
Click to expand...

14d067a6-03a2-4569-b805-28c44bbf6350 2025-06-12 15:39:32.421152 97.83% [NOTICE] sofia.c:7985 Hangup sofia/internal/1001@mypbx.com:5060 [CS_NEW] [INCOMPATIBLE_DESTINATION]
Click to expand...

There's seperate codec configs for the switch, extension, and device, examine/compre them all. g729 may require licencing to transcode, so while it may work in passthrough it may not otherwise. If not using Fusion's device provisioning give that a try, good smart people have contributed to the templates.
 
This is an issue with RTP. SIP worked to establish the call but Freeswitch found no Suitable RTP Candidates.

Code: 
[DEBUG] switch_core_media.c:4254 Searching for rtp candidate.
[DEBUG] switch_core_media.c:4254 Searching for rtcp candidate.
[DEBUG] switch_core_media.c:4307 sofia/internal/1001@mypbx.com:5060 no suitable candidates found.

Common causes for "INCOMPATIBLE_DESTINATION" and SIP 488:
  1. SDP offers only unreachable IPs or ports. (Often seen if the endpoint is behind NAT and FreeSWITCH is not correctly configured for NAT traversal.)
  2. ICE negotiation fails.
  3. Firewall or NAT is blocking RTP or SIP ports.
  4. SIP profile not configured with the correct external IP.
 
  • Like
Reactions: PrettyBrutalXperience-Guy
the pbx is on the internet just the firewall on the system and it works everywhere else so that can't be it. I'm looking to see if the firmware on the yealink is custom to GOTO.COM I was told by the previous IT provider they sometimes do that. Codecs are being negotiated. I slimmed it down to PCMU and PCMA removed G729.
the yealink is currently behind a ubiquiti gateway which we want to remove since we took over and put a fiber feed in. details to follow
thanks leon
 
It's most likely the client side with the Ubiquiti gateway that has an issue with routing problems.
To confirm, take the phone and put it on a different connection. If you can't take it out of the client's side, use an LTE modem.

You can check the third number in the firmware (Example 86.125.x.45). If x is not zero, then the firmware is custom.
 
I only run TLS for all phones for this reason. I haven't had any routing issues in 6 years after we switched. Before that, each customer was a whole new challenge.
 
ok we took out the Ubiquiti gateway and still having the same issue. Got TLS working as well and still get the incompatible errors. i got some pcaps as well. it had 96.86.0.153 firmware which I have no idea where they got it from. We put the latest 96.87.0.15 on it. Codecs are matched PCMU and PCMA. The pbx works with everyone else and even our own yealink which we are going to look into tonight.

The only other thing I can think of is factory default the phone.

Leon
 
so we factory reset the device and still have the problem. It seems the Remote SDP has encryption in it. I've turned off SRTP or have it optional. to no avail. We're using TLS and I accept any certs. Using UDP get similar results.

here's what it looks like:

Code: 
 bf808ccf-64ec-46cb-b394-55f469451a29 2025-06-19 15:42:29.991214 98.00% [DEBUG] sofia.c:7503 Remote SDP:
 bf808ccf-64ec-46cb-b394-55f469451a29 v=0
 bf808ccf-64ec-46cb-b394-55f469451a29 o=- 20007 20007 IN IP4 10.1.10.100
 bf808ccf-64ec-46cb-b394-55f469451a29 s=SDP data
 bf808ccf-64ec-46cb-b394-55f469451a29 c=IN IP4 10.1.10.100
 bf808ccf-64ec-46cb-b394-55f469451a29 t=0 0
 bf808ccf-64ec-46cb-b394-55f469451a29 m=audio 12300 RTP/AVP 0 8 9 101
 bf808ccf-64ec-46cb-b394-55f469451a29 a=rtpmap:0 PCMU/8000
 bf808ccf-64ec-46cb-b394-55f469451a29 a=rtpmap:8 PCMA/8000
 bf808ccf-64ec-46cb-b394-55f469451a29 a=rtpmap:9 G722/8000
 bf808ccf-64ec-46cb-b394-55f469451a29 a=rtpmap:101 telephone-event/8000
 bf808ccf-64ec-46cb-b394-55f469451a29 a=fmtp:101 0-15
 bf808ccf-64ec-46cb-b394-55f469451a29 a=ptime:20
 bf808ccf-64ec-46cb-b394-55f469451a29 a=crypto:1 AES_256_CM_HMAC_SHA1_80 inline:/7z42ZPKT20Na1Emq/XNquuqjlQpplLTMS7HpBfdcr4tEgEirhtAITP2W7n+lQ==
 bf808ccf-64ec-46cb-b394-55f469451a29 a=crypto:2 AES_256_CM_HMAC_SHA1_32 inline:iL592IAXY7WE710Ie5JDAp0p5c9HMuUvfYcz8g2nzN6v0krg1WqFSk8SYyUB+Q==
 bf808ccf-64ec-46cb-b394-55f469451a29 a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:JciUy07y4iEY9SHAGmUme36snTO+N2GGoCVMZVF+
 bf808ccf-64ec-46cb-b394-55f469451a29 a=crypto:4 AES_CM_128_HMAC_SHA1_32 inline:7fCUiMSOFWcrkhuPELwa+lHo/grY+zwcOlTrOoqx
 bf808ccf-64ec-46cb-b394-55f469451a29
 bf808ccf-64ec-46cb-b394-55f469451a29 2025-06-19 15:42:29.991214 98.00% [ERR] switch_core_media.c:5387 a=crypto in RTP/AVP, refer to rfc3711
Click to expand...
My Grandstreams don't do this at all. Also, this is on the latest Yealink codebase 96.87.0.15.
I exported the config and we're going to try it on one of our Yealinks to see if it works out of that network. Never had this much trouble getting a phone to work.

Leon
 
Its been a while, but a have a vauge recollection of having to mess with something in openssl so accomodate Cisco 303s. Copilot says:


RFC 3711 defines the Secure Real-time Transport Protocol (SRTP), a profile of RTP that adds confidentiality, message authentication, and replay protection to media streams like voice and video over IP. It was published by the IETF in March 2004 and is widely used in VoIP systems, including FusionPBX and FreeSWITCH.

Key features include:

  • Encryption using AES in counter mode (AES-CM)
  • Message authentication via HMAC-SHA1
  • Replay protection using sequence numbers and rollover counters
  • Support for both RTP and RTCP streams
In your case, the Yealink phone is sending a=crypto lines in the SDP under RTP/AVP, which violates RFC 3711—it requires SRTP to be negotiated under RTP/SAVP or RTP/SAVPF. That’s why FreeSWITCH logs a=crypto in RTP/AVP, refer to rfc3711 and throws INCOMPATIBLE_DESTINATION.

To resolve this:

  • Ensure the Yealink is set to use SRTP with enforced media encryption (not optional) and that it uses RTP/SAVP.
  • Alternatively, disable SRTP entirely on both ends if encryption isn’t required.
  • If TLS is enabled for signaling, make sure media encryption aligns with it.
You can read the full spec on RFC Editor’s site or check out the Wikipedia summary for a lighter overview. Let me know if you want help crafting a Yealink provisioning template that avoids this.


While I'd advise using SRTP because I beleive in privacy, encrypted signalling is all that's needed to keep your SDP from being tampered with, haven't seen networking equipment mess with RTP strems except for QoS or port level blocks.
 
I hope you also made sure that TLS actually worked 100% on some device. It's not always easy to get it going the first time. So it may seem like nothing works until the right combination is used. There is a lot involved in setting it up
 
yeah we got it working thursday evening. TLS works with our GS phones and it also worked on the Yealink with our work domain. It was something on this customers domain that was possibly off besides my extension that got changed

Thanks for the assist. Leon.
 
You must log in or register to reply here.
Top Bottom