cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2451
Views
0
Helpful
6
Replies

Extension mobility - Call routing issue (get UPA without MLPP)

Hello

we have a 8.6.1 CUCM Cluster with EM enabled.

It works as expected but, sometime some users on some (random) phones are still able to login but they are not able to place the call and they hear the message "the precedence used is not authorized for your line, please use an authorized preference or ask your operator for assistance"

IF the same user logins to another phone (with the same device CSS, device pool, etc configuration) the user is able to call.

The only workaround we found is to delete the phone from CUCM and rebuild it. With this procedure the call are routed as expected.

Any help to find a better solution will be greatly appreciated

Thanks in advance

Stefano                  

      

Update:

I added the trace of a disconnected call: but I'm not able to find any particular reason for the disconnection.

from phone SEPXXXXXXX (internal number ABCD, fqdn 0XYZWKABCD) to external 000NNNNNNN

6 Replies 6

To update the issue, the message is the UPA  but we are not using MLPP.. And this issue disappears by deleting the phone and re-creating it with same settings

Jaime Valencia
Cisco Employee
Cisco Employee

It sounds like you have MLPP configured.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

We don't have MLPP configured...

Hi Gianstefano.
Are working phone and non working phone same model and have the same firmware version?
What kind if IP PHONE are you using?

Regards

Carlo

Sent from Cisco Technical Support iPhone App

Please rate all helpful posts "The more you help the more you learn"

Hi Carlo

issue appears randomly on different models of working phones (7942, 7960 and 7965). AFAIK they have the same firmware version, the one they get from CUCM: We are able to solve the problem deleting the phone from CUCM and then re-creating it. Tomorrow I'm planning to investigate further using RTMT and tracing logs from a failing phone...

Update

Facts we gathered so far:

1. on the log we see: CI=38337938 Block NoPotentialMatchesExist OffNetpatternUsage =5requestID =0

    it seems that the Line CSS is not in place and the CUCM "sees" only the Device CSS, so blocking the call.

2. Every roaming user with this phone is not able to call,

3. if the same user goes to another phone he/she can call.

4. If we delete the phone and re-create it (with same settings) then it starts working as expected.

I think we should open a TAC Case.