Yealink T58 & Door Phone

[Jason Aday]

Hello,
I am working on an install where a client was trying to use an existing Axis video door phone, the doorphone button would dial an extension with a Yealink T58A. When the button was pushed, the T58A would never ring, other Yealink phones in the ring group would, (T42S), but not the T58A. I thought it was because it wasn't a supported doorphone, so we picked up a Fanvil i31s and I'm testing on our in house system, it's doing the same thing, won't ring the T58A. If I open the 3cx mobile app tied to that extension with the T58A, it rings just fine.

I can call the extension of the i31s or the Axis doorphone, it auto answers and I get video, but the DSS key won't call a T58A.

What is it about the T58A that causes it to not ring at all? Is it something about the video feature that's causing it not to? Has anyone ran into this problem?

Thank You,
Jason

 

[JohnS_3CX]

Hi Jason,

Not clear on whether you are actually calling a ring group extension (which the T58A is part of) or if you are ringing its extension directly.

Video should be unrelated, this is negotiated after the device rings and picks up.

 

[JohnS_3CX]

Also please take a look here for the i31S if you haven't already https://www.3cx.com/sip-phones/fanvil-sip-doorphones/

The first BLF key can be set to a “Speed Dial”. This provisions the doorphone to call the specified number when the button is pressed, e.g. to call the extension of the T58A

 

[Jason Aday]

Also please take a look here for the i31S if you haven't already https://www.3cx.com/sip-phones/fanvil-sip-doorphones/

The first BLF key can be set to a “Speed Dial”. This provisions the doorphone to call the specified number when the button is pressed, e.g. to call the extension of the T58A

Hello John,
During the initial setup, I set it to the extension of the T58A, when that didn't work, I created a ring group with just the T58A, that didn't ring either, so I added a T48S extension into the ring group and it will ring the T48S just fine, but not the T58A. When answering the T48S, it answers, I hear can both ways and press the * key to trigger the door unlock.

The T58A never rings, even though in the log it says it's trying.

-Jason

 

[Evolute IT]

Hello John,
During the initial setup, I set it to the extension of the T58A, when that didn't work, I created a ring group with just the T58A, that didn't ring either, so I added a T48S extension into the ring group and it will ring the T48S just fine, but not the T58A. When answering the T48S, it answers, I hear can both ways and press the * key to trigger the door unlock.

The T58A never rings, even though in the log it says it's trying.

-Jason

Are you sure your T58A is well configured? Please run a packet capture on 3CX and on the T58A so we can see why the call isn't getting there.

This sounds like either blacklist or config issues.

 

[JohnS_3CX]

Please Check on the T58A directory, there is a blacklist.

See if the doorphone extension has been added there by mistake.

 

[Jason Aday]

I checked the blacklist and it's empty on the T58.

I changed the i31s back to only ring the extension of the T58, ran a packet capture and attached it.

If i let the door phone ring the extension, it eventually hits voicemail, so it's going to the correct extension, the T58 just never rings.

This system is hosted in our datacenter, I have tried provisioning the T58 via local network and Direct STUN, but both get the same results.

 

[Evolute IT]

I checked the blacklist and it's empty on the T58.

I changed the i31s back to only ring the extension of the T58, ran a packet capture and attached it.

If i let the door phone ring the extension, it eventually hits voicemail, so it's going to the correct extension, the T58 just never rings.

This system is hosted in our datacenter, I have tried provisioning the T58 via local network and Direct STUN, but both get the same results.

What is which in that capture?

• Extension "6000 - Back Door" -> I guess is the doorphone
• Extension "9521" ?
• Extension "9522" ?

From what I see here, the call is cancelled due to a timeout. You would need to check the Activity Log in 3CX to know the exact reason for that.



Have you tried configuring the doorphone to do a Direct IP Call to the T58A? Make sure to enable IP Calls on both and try that. Since they are both local, it shouldn't be an issue.

 

[Jason Aday]

I just tried to do a Direct IP call from the I31s to the T58, but it still doesn't ring. I can do a direct ip call from the T58 to the i31s and it answers immediately with video.

9522 is the extension of the T58, 9521 is another T58, but not being used to test this issue.

I checked the activity log in 3cx, but can't find anything about why it was cancelled other than a no answer and then forwarded to voicemail.

 

[Jason Aday]

I tried doing a direct ip call between to yealink phones on the same network and it doesn't work either, so not sure if that's a great test. Direct IP call is enabled on both phones.

With the original setup, the BLF of the T58 extension shows ringing, but the phone itself doesn't ring and I know I've said it a few times now, but it's only the T58 that doesn't work.

 

[Jason Aday]

attached is a packet capture from the T58, the capture was running when the door phone was attempting the call.

I see a rejected state in the VoIP call, but that's from the 3CX side it looks like.

I appreciate you helping with this issue.

 

[Evolute IT]

Now, since this is an isolated issue, please verify your codecs orders on each and make sure the H.264 is enabled everywhere.

If it still doesn't work, well, we have an issue here. I tried reproducing the issue using other videophones I have here, but it didn't tell me anything new.

 

[Jason Aday]

The video codec was set to H264HP first, and H264 second, so i moved H264 first, but that didn't make any difference. I verified the order of the audio codecs match the order of the phone under provisioning in 3CX.

 

[Evolute IT]

The video codec was set to H264HP first, and H264 second, so i moved H264 first, but that didn't make any difference. I verified the order of the audio codecs match the order of the phone under provisioning in 3CX.

Do they also match the extension's codecs? Under Options.

 

[Jason Aday]

Under options, I don't have any codec options, just under Phone Provisioning

 

[Evolute IT]

Under options, I don't have any codec options, just under Phone Provisioning

Sorry, under Settings -> PBX

 

[Jason Aday]

I checked those and they matched under the phone settings. I tested a call last night and it started working. The only thing I had changed was moving the H264 codec up, but when I tested right after that, it didn't work.

I'm not sure what happened, but it's working right now. I will take it onsite and test with the customers T58.

Thank You Frederick for your assistance, much appreciated.