0

Yealink phone does not register after changing its extension number.

Alex Benítez

July 27, 2018 04:55

None

Follow

Hi friends

I am experimenting this problem in a YEASTAR S50 IP PBX:

The customer is changing a extension. The current number is 411, the new number is 440. 
The customer defined the extension 440 in the PBX.
The old extension (411) has not been erased
The customer changed the user and password for sip registration in the phone (Yealink  T49G).
The phone never registers

I checked the security log (no ip blocked is seen).

I took an asterisk trace

This is the error shown:

[2018-07-25 16:23:01] NOTICE[26319]: res_pjsip/pjsip_distributor.c:440 log_unidentified_request: Request from '"Flavio Tepper" <sip:440@172.26.2.11>' failed for '172.26.2.30:5060' (callid: 0_2534011442@172.26.2.30) - No matching endpoint found

[2018-07-25 16:23:01] NOTICE[15831]: res_pjsip/pjsip_distributor.c:440 log_unidentified_request: Request from '"Flavio Tepper" <sip:440@172.26.2.11>' failed for '172.26.2.30:5060' (callid: 0_2534011442@172.26.2.30) - No matching endpoint found

Additional information:

- When the customer put the user 411 n the IP phone the register is ok

- When the customer changes the user to 440 the IP phone fails to register

- When the customer changes back the user to 411 the registration is successful.

Why the phone with the new extension can not register and how can I fix it?

Please help me!

• Facebook
• Twitter
• LinkedIn

7 comments

• 0
  
  James Sumner July 27, 2018 05:04

  Sorry if this seems silly but. Have you rebooted the PBX since the changes?

• 0
  
  Larry Neblett July 27, 2018 12:23

   

  There is not enough info by which to know where the fault is and correct. 

   

  It is not known how the phone, when 411, was provisioned -  manually or by the system?

  411 was not deleted, but it is unknown if there is a configuration file created by the system provisioning (if done this was) may still be in play. If provisioning was done by the system, you need to delete the extension as shown in the auto-provision section so that the association is no longer between 411 and the MAC address of the phone. 

  You should change the details in the extension settings in the PBX so as no longer see or identify the  extension 411 to the user of the phone....so that it will not show in LDAP or other locations  to be still with user X. 

  You may want to (should) consider factory resetting the phone so that it has no residual info left over from any system or user settings done previously. 

  When reset, use the auto-provisioning function to locate the phone and then assign to 440 with whatever system allowed settings you want and then see if it registers. If so, then you can manually provision whatever other settings you need that the system may not currently support. 

   

• 0
  
  Alex Benítez July 28, 2018 10:28

  Hello Larry

  As far as I know extension 411 was manually provisioned.

  Thanks for your comments.

• 0
  
  Alex Benítez July 28, 2018 10:29

  Hello James

  No. I have not rebooted the system.

• 0
  
  James Sumner July 29, 2018 01:36

  You will be amazed what I've found in background is not set until a reboot is done. You can do this through maintenance. Like picture below. Let me know if this fixes the issue.

  

• 0
  
  Jonathan November 16, 2018 23:06

  Your phones ip address has probably been blocked in auto defense

• 0
  
  Rasheed June 25, 2019 20:00

  Mr. Jonathan , YOU ARE GENIUS. I was hitting my head on this since 2 days.