Forums Read-only archive

Yealink Incoming Call Trouble

5 posts · Brekeke PBX Forum

bryanint Original post
1. Brekeke Product Name and version:Brekeke PBX, Version 2.4.7.3 , Multi-Tenant

2. Java version:

3. OS type and the version:

4. UA (phone), gateway or other hardware/software involved:Yealink T26

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :

6. Your problem:

We have several Yealink T26 phones that are working fine on outgoing calls. The trouble seems to be on incoming calls. There appears to be some kind of timer that once it expires after the phone has been idle that the phone wont ring.

We had the same problem with Cisco 504G phones but once we enabled the two NAT settings on the extension tab the trouble went away.

Does anyone know how to fix this trouble using Yealink phones :?:
Harold
Are these Yealink phone located behind NAT?

If they are, let you try the following.

- In the phone, set the shorter REGISTER expiration time .

OR

- In the SIP server,
set the [Keep address/port mapping] = "on"
set the [Interval (ms)] = shorter value (5000 for example)
bryanint
I believe we are behind NAT.

The REGISTER expire on the phone is at 120.

I changed the value from 12000 to 5000.

And port mapping was "on".

I'll go by the site tomorrow to test.

Thanks,
-B
Harold
FYI:

You can tune the client's REGISTER expiration with the following DialPlan rule.
--------------------------------
[Matching Pattern]
$request = ^REGISTER

[Deploy Pattern]
$action = register
&net.registrar.adjust.expires = 120
--------------------------------

With this rule, you don't have to tune the expiration at each phone.
bryanint
That is very cool. Thanks

It appears that my problem is solved. I'll let the customer try it for several days just to make sure.

Thanks for the help.