[cisco-voip] FW: Calling Party - Call Forward - Route Lists

[Bob Fronk]

We have discovered that now we must reset the MCGP gateway that terminates the PRI to get the calling party ID to present correctly on forwarded devices.  Also, if the same number calls more than once, the first time the calling party ID is presented as the office main number.  If the same calling party calls a second time, the calling party ID is presented to the forwarded device correctly.

I am going to say this is some kind of bug, or maybe a timing issue?

Any input would be appreciated.




From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net]<mailto:[mailto:cisco-voip-bounces at puck.nether.net]> On Behalf Of Bob Fronk
Sent: Monday, March 12, 2012 9:27 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Calling Party - Call Forward - Route Lists

Good morning group.

CUCM Version - 6.1.2.1000-13

When calls are forwarded or a remote destination is configured, the caller ID is presented to the PRI and is passed to the number being called.  This is the expected result.

Example - 123-555-7890 calls extension 1105.  1105 is forwarded to 678-9012.  The originating caller ID of 123-555-7890 is seen on 678-9012.

However, at some point during the day, this stops working and the main number is presented to the forwarding device rather than the calling party.  If I reset the Route lists, then this starts working correctly again.  Then later, it stops, reset works, stops.... On and on.

I cannot find a correlating reason why this happens.

Thanks for any input or advice.

Bob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120314/89b675ba/attachment.html>