thirdlane Connect problem with switching back to desk phone

Hi,

Make sure NAT Keepalive is set on the desk phone and ensure NAT is enabled on TL extension. This has fixed issues with OB calls working & IB calls failing for us behind NAT before; however I'm not sure whether this will help with TL Connect related issue.

Thanks, Matt. I can't find any settings on the Yealink phone for Nat Keepalives, although it may be called something else. I'll put the phone on an outside address and see if that works, although I can't keep it there, it may tell me something.

Anyone else? Thirdlane?

Update: From Matt's suggestion I put the phone on a non natted ip address and the same problems exactly persist.

would love to get Connect working consistently, it is a great feature, but buggy at least on our system HELP.

Doug

Hi Doug,

The keep alive setting on the Yealink can be found under Account --> Advanced. There are 2 settings on this phone you should pay attention to: #1 Keep Alive Type = Options and #2 Keep Alive Interval (Seconds) = 30

Based on your test with a non-NAT address it likely won't help, but it's worth a try...

I changed Matt's Keep alive suggestion and when testing today it still does no work. Is anyone else at Thirdlane listening Alex, somebody?

This has no any relation to NAT or Keepalives. The issue in nutshell is in the chan_sip... Asterisk chan_sip could have only one contact per AoR (one registered sip phone per account at a time), and only one set of settings per contact. This is why switching mechanism exists. When Connect switches to WebRTC mode, we restrict any register messages coming to Asterisk except thru WS per account. This blocks any registrations from TCP, UDP, TLS, and allows only Connect to register and don't fight for it right to be reachable, with the desk phone, which would not even be able to support all those ICE and DTLS-SRTP settings which are mandatory for Connect. Now, when you switching back to track your desk phone within Connect, your phone "does know nothing" about any switch happened, and we don't have any good way to tell this to your phone. So it should receive some poke, to re-register, or you should wait till next registration, based on your phone registration interval. This solution was applied as temporary, with the idea in mind, that people will not be switching back and forth all the time, and when someone will switch to the desktop phone, he will be responsible to poke the phone. We do realize that this is not an ideal solution and right after initial release we started a big project that aims to fix this and
the huge amount of related issues. Connect support for simultaneous login on multiple devices per single account alongside with one registration per sip account is planned for the next major release. This means that you will be able to have few Connect instances (home/work/mobile) and your desk phone working simultaneously. We will publish the blog post about next major release, that will explain all the differences, improvements, and benefits once it will be ready, before release.

Ok, thanks for the explanation. this may help others. I will tell customers they need to "poke" the phone when they get switch back.

Doug

Unless it is a very large system, I would set the phones to re-register every 60 seconds.

Just found the place on the phone config to tell it to re-register every N seconds, thanks mattdarnal, this is the fix.