Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CUCM 7.1 Sip -> unique caller ID settings not working

Status
Not open for further replies.

araq44

MIS
Aug 19, 2010
6
US
I just got pushed onto a CUCM 7.1 to manage and I am having trouble with the outbound caller IDs. The CM is in a shared space so everyone wants their DID to show on the outbound caller ID and the main line number is showing every time.

*I checked settings in Directory Number under Line 1 on Device XXXXXXXXXX and making changes only changes caller ID information on internal calls.

*I also checked on Directory Number Configuration Alerting and ASCII and still no change.

*I played around in the Device -> Trunk -> Trunk Settings with no luck

I am an Aesterik's guy pounding my head against the desk in a Cisco world right now. Any help would be great. Thanks guys.

My fingers are crossed that someone knows.

-E-
 
Instead of the alerting name change the external calling number entry for each user to the desired outbound ANI.
Also make sure in the route patterns that you have checked the allow device to show calling number tab.
If is still not working you will need to debug your sip trunks to see if the ANI you are sending is being overwritten by the SIP provider
 
whykap, Thank you for your help!

I have fixed the problem at hand. Here is how I repaired the unique caller ID out bound issue with CUCM7.1

* Double checked with carrier and CID was left open to our switch

* In CUCM Admin -> Route List -> Route List Details -> Calling Party Tran Mask (was set to main number, so I cleared it).

* In CUCM Admin -> Route List -> Route List Details -> Turned Mask "ON" as it was set to "Default"

Your route patterns comment sent my mind in the right direction. Thank you again. The call manager I had pushed onto me is the most poorly configured device I have ever encountered and it is making me trip up on small issues due to the fatigue of dealing with larger issues. Virtual Beer on me buddy.

-E-

 
For what it's worth, I went from Asterisk to CUCM, and while a little bit of a learning curve, I've found CUCM to be overall a much better solution. I started with CUCM 6.x and am now running 7.x. Played with 8 but no current plans to upgrade. I've found the reliability to be much better than the Asterisk-based solutions, also the call quality. I run all the phones using the SCCP protocol and have deployed CUCM on various other sites as well both centralized with SRST and multi-site clusters. Don't give up on it, it can be a bit daunting at first, but it is a well designed system. I believe if you give it time, you'll come to like it :) Any questions, this is a great place to come!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top