We have forced auth codes setup on our CUCM v7.x cluster for all of our users. We are at the start of a migration from a Nortel Meridian 81c PBX to all CUCM. PSTN is connected to the Nortel PBX and we have a QSIG trunk setup between the Nortel and a 2951 ISR for the CUCM. Calls destined for the PSTN from the Cisco side are forwarded to the Nortel.
We require forced auth codes for all of our users in order to make calls out to the PSTN. This is for billing purposes. We'd like to keep out billing system the same and not have to initially make any changes to the billing system as all PSTN calls would still go through the Nortel.
Is there any way for CUCM to forward the FAC digits that allow the user to make a call out to the PSTN over the QSIG trunk to the Nortel PBX? If we can get the FAC code to append to the Called Number when sent to the Nortel PBX, the Nortel would be able to handle all of our billing during the transition (and we don't have to touch that system). The Nortel would strip the FAC code and send it to our billing provider for billing.
The way I have seen this handled is that the CUCM has a route pattern that people use when they need to place a call using FAC.
This pattern routes to the Nortel. The Nortel gives secondary dial tone and then the user enters their FAC followed by the number they wish to reach. This was a CM 4.2 and Nortel integration using MGCP. I am not sure what was configured on the Nortel side. On the CUCM side it was a standard route pattern. The CUCM had no locally configured FAC. Meaning, the CUCM did not challenge the user.
The only other option would be to have people dial the entire digit string, with the FAC and pass the whole thing to Nortel.
AFAIK, there is no way to challenge a user with FAC on the CUCM and then pass those digits along to the Nortel.
Looks like we are just going to use the CDR records generated on the CUCM to do our billing against. Once we found the setting to enable the FAC to show in the CDR that gave us all the info we need to do billing. Of course now we have to have our billing provider build another program to run billing against -- which is what we wanted to avoid in the first place. (we do billing off the auth codes) The show FAC in CDR setting is found here for anyones future searching reference:
System -> Service Parameters -> Advanced-> Clusterwide Parameters (Device - General) -> Show FAC in CDR
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...