No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

U1960 - Issues when configuring ONLY number

Publication Date:  2018-03-05 Views:  89 Downloads:  0
Issue Description

Customer reported an issue when configuring the ONLY service for some specific extensions in order to ring at the same time, but he encounters the error displayed as : "Terminal Number 584 configuration failure. This number cannot be bound to itself, or has been activated". 

The firmware version that is running on the U1960 unified gateway is V200R003C00SPC500B011

Handling Process

During the handling process we have requested from the customer the configuration file, extensions involved that are receiving this error when configuring the ONLY service for them and also provided him the possible causes for this report:

- The ONLY service is disabled for the user

- The number to be bound (intra-office user) has the ONLY service

- The number to be bound does not exist

- The ONLY service is enabled for the number to be bound to another ONLY number

Asked the customer to run the show subscriber dn <string> type newservice command to check wether the primary terminal or the number to be bound has ONLY service and also the show subscriber command to check wether the number to be bound exists.


Customer provided the below output for each:


[%eSpace U1960]>show subscriber dn 594 type newservice

 

New Service

 

----------------------- ------------ ---------------

  Rights                  Register     Information  

----------------------- ------------ ---------------

NORMAL                  Y                           

THREE_PARTY             Y                           

CALL_WAITING                                        

WAKEUP_CALL                                          

BUSY_CALLBACK                                       

SECRETARY_STATION                                   

PARALLEL_RING_SERVICE   Y                           

SERIAL_RING_SERVICE     Y                           

OPERATOR DISCONNECT     Y                           

TONE_SUPERVISION        Y                           

OPERATOR INSERT         Y                           

SUPER_RIGHTS_USER                                   

UNICALL                 Y                            

ABBREVIATIVEDIAL                                    

BUSY_CALLSAVE                                       

CLIP                    Y                           

CALLLIMIT                                           

DDS                                                  

ABSENT_USER                                         

CFU                                                 

CFB                                                 

CFNR                                                

CFO                                                  

HOOKING_TRANSFER        Y                           

AMEND_PASSWD            Y                           

SECRETARY_SERVICE                                   

CANCEL_ALL_NS           Y                           

PICKUP_SPECIAL          Y                           

PICKUP_IN_GROUP         Y                           

MULTICALLS              Y                           

INSTANT_CONF            Y                           

CALLPARK                                             

CNIP                    Y                           

EXTENSIONNUMBERPORTABLE Y                           

 

------- Matched record number : [34] -------

 

====  Command executed success !  ====




Numbers 584, 585, 586, 587 come up with the same error when trying to add them as an intra-office number to 594 service configuration options as it can be seen below:


 






A remote session has been scheduled and afterwards we noticed that the customer is also using a BMU and that all the affected users have been configured on the BMU using the IsJoint feature set to YES (Linked UC number) under SIP Maintenance.




Root Cause

Since the customer is also using a BMU and all the affected users were configured on the BMU using the IsJoint option set to YES (linked UC number) under SIP Maintenance and they could not be configured with the ONLY service.

Solution

The solution for this case was to delete for one user affected the Device ID pc user created and then to test again to configure the user with the ONLY service and confirm its functionality. The system generates two Device ID for each user created as in our example 584 and 584pc with this option set to YES and in this case these users cannot be configured with the ONLY service.





END