Yealink Forums

Full Version: Local Sip port on T46
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,

I've just purchased a Yealink T46 phone and I want to register it with 2 different accounts (line 1 and 2) to my PBX (3CX).

Now the phone registers correctly on the PBX but both extensions register on the same SIP port (5065) which obviously gives problems with incoming calls.

On other phones I have I can set a local SIP port per account but on this phone I cannot find this setting? Can anyone tell me where I can set the SIP port for account 1 to 5061 and the SIP port for account 2 to 5063?

Thanks in advance!
Hi,

In Yealink V80 and higher version, all accounts use one port to register. You can change the port via web interface->setting->SIP->local SIP port.

I think some of your phones run V73 or lower firmware version, so it support different accounts with different ports. Please check.

I want to explain again why we optimized it in V80 and higher version. (Old mechanism: SIP local port for each account; New mechanism: SIP local port for all accounts )
Before when we are using old mechanism, we really occurred may issues from many cusotmers. Actually, the old mechanism is not a standard one. As for SIP standard, the default port should be 5060 for all accounts. If we are using old mechanism, each account have to use different ports. That's not following the SIP standard will bring many trouble for customer.
And also the main SIP phones vendors are all using the new mechanism, we are all following the Standard.
The Polycom and Cisco also follow the same mechanism.

You said the phones have incoming calls problem, please tell me detail issue scenario and help us to get the trace files.
You will know the method via FAQ below.
FAQ: http://support.yealink.com/faq/faqInfo?id=313

And please tell me how many phones in your side and 3CX version.
The problem is that 1 of the extensions keeps losing its registration while the other extension stays registered without problems.

In the 3CX is see the extension as not registered and other phones cannot contact that extension anymore when it appears as not registered. When I look in the T46 status page it says the extension is still registered.

I am using 3CX version 14 with latest updates.
There are 9 other phones connected to that PBX, all in the same office and network and they all work fine. The other phones are Cisco's and Yealink T41's.

The T46 has its IPv4 config set to manual (as all other phones do also).
Extension 1 and 2 have exactlty the same settings on the accounts page (other than their username and password).
(07-28-2017 09:35 AM)JamesC Wrote: [ -> ]The problem is that 1 of the extensions keeps losing its registration while the other extension stays registered without problems.

In the 3CX is see the extension as not registered and other phones cannot contact that extension anymore when it appears as not registered. When I look in the T46 status page it says the extension is still registered.

I am using 3CX version 14 with latest updates.
There are 9 other phones connected to that PBX, all in the same office and network and they all work fine. The other phones are Cisco's and Yealink T41's.

The T46 has its IPv4 config set to manual (as all other phones do also).
Extension 1 and 2 have exactlty the same settings on the accounts page (other than their username and password).
Can you tell me the firmware version of T41P and T46?
I think it's better that you can apply the trace files for us to check more.

And suggest you can descrease Server Expires then test agian.
(08-01-2017 08:38 AM)Karl Wrote: [ -> ]Can you tell me the firmware version of T41P and T46?
I think it's better that you can apply the trace files for us to check more.

And suggest you can descrease Server Expires then test agian.

The T41 is on: 36.81.0.61
The T46 is on: 28.80.188.16

I already set Server Expires to 120 but that made no difference. Settings the session expires timer to 90 seems to make a difference but I have to wait some more time just to be sure.
[edit]
Setting the session expire timer made no difference, the extension does not re-register.
Making a pcap is almost impossible as it sometimes takes 24 hours before this problem occurs.
[/edit]

[edit2]
Upgraded the T46 to latest firmware (28.81.0.110) yesterday but it does not solve the issue.
[/edit2]
We have disabled 1 of the 2 accounts and tested for a couple of hours and everything seems fine, no problems so far.

Analyzing the issue a little further showed that when we enable account 2 this account only receives incoming calls when account 1 is idle. When account 1 is calling, the PBX gets a 486 from account 2 when trying to offer a call to it.

Enabling account 2 also gives re-register problems after a couple of hours (all random; sometimes 3 hours, sometimes 6 and so on...).

What we have done so far:
- replaced utp cable
- replaced power adapter
- upgrade to latest firmware
- deleted both accounts and created them again in PBX
- deleted both accounts and created them again in the phone
- placed a Cisco 504 and a Linksys SPA942 at the users desk with same accounts and this works fine

What else can this be? We really suspect the local SIP port as both accounts map to the PBX with port 5060.
This issue is still not resolved.

Can anyone comment on this?
Please try to get the trace files, so we can check more?
Or you can apply test accounts for us to check locally.
Reference URL's