hmm okay, thanks so much Jaime, this is an existing config, so i am not sure why it was configured this way. How should I go about making the change from 1-4 to 1-24 ? Remove the existing config or is it possible to change the pri-group timeslots from 1-4 to 1-24? This is a failover pri
... View more
Hello, i have a question about the following (this is 1 of 3 pri's on a router) : controller T1 0/2/0 cablelength long 0db pri-group timeslots 1-4,24 service mgcp The pri is configured as "pri-group timeslots 1-4,24 service mgcp" What does 1-4 mean ? it is only configured to use 4 channels, plus 24 for D channel? correct? I believe it should be an entire PRI. i have a feeling there arent enough resources on the router is there a way to check this ?
... View more
If i remove the service parameter, then there would be no need to create a transformation pattern to remove the 9 because the service parameter is what is adding the 9.
... View more
This is exactly how i have set it up. I have decided to test it only for 1 phone by using the phone settings instead of the device pool because the device pool has all of our phones. However it doesnt seem to be working. My next option was trying the translation pattern on the device pool, but again, i can not test durning our production hours. Thank you so much for your reply
... View more
Sure but if i do that, then the 91 will no longer be present for my users to return the calls with easy. I dont want them to have to edit the number to return a missed call.
... View more
There is not translation pattern adding a 9 . The 9 is being added from the option in service parameter > CallManager > Advance, "Incoming Calling Party National Number Prefix - Phone ". Below in bold is basically what we are doing. --- "Incoming Calling Party National Number Prefix - Phone: This parameter defines the number, up to 8 digits, that is prefixed to an incoming national number in the signaling to the following terminating devices: on the phone and in the Missed Calls and Received Calls directories; to CTI, TAPI, and JTAPI applications; to voicemail ports. The service parameter, Incoming Calling Party Number Prefix - Apply To controls which devices receive the prefix specified in this parameter. Be sure to examine the value in the service parameter, Incoming Calling Party Number Prefix - Apply To, to be certain that the prefix is being sent to the appropriate terminating devices. Using this parameter provides a means to help you identify national numbers, if necessary. This parameter allows you to prefix specified digits to the calling number of an inbound call on the basis of the Type of Number field in an inbound offered call that gets terminated at an IP Phone. For example, a national call in USA from 4085551212 could get prefixed with 91.
... View more
I was refering to a typo - i had said translation pattern instead of saying transformation pattern. It seems like the transformation pattern is not being hit when the call comes into the device. The 9 still shows up
... View more
I am sorry i wrote the wrong thing ( typo fixed now ), but yes i am using Transformation Pattern. We are not using the device pool . I tested it with 1 phone using the option "Remote number - Calling Party Transformation CSS " under the phone settings
... View more
We currently have configured the setting " Incoming Calling Party National Number Prefix - Phone " to add the "9" to the calls that enter the organization so that our users can simply call the number back without having to edit the number to add a "9". With doing this though, calls are being displayed as 91XXXXXXXXXX on the phones. I would like to remove the 9 from being displayed when the call is ringing the phone. From what i've found online, i am should use a Calling Party Transformation Pattern I have tried this but it does not seem to be working out for me. I created a new CSS and Partition for the Transformation Pattern , and have selected the new CSS for the option of " Remote number - Calling Party Transformation CSS " under the phone settings. I tried the translation pattern of "9.1" and also " 9.1[2-9]XX[2-9]XXXXXX" with discard digits of PreDot. System version: 9.1.1.10000-11 Am i missing something here ? Thank you in advance
... View more
The NYC site would be only about 10-15 users. You bring up a very good points on why to go with option 1 about splitting the cluster geographically . That makes more sense since it will only be a small site and we will have frame relay between the sites . Thank you very much Chris,
... View more
We have an LA headquarters with 2 UCS servers. At the moment is it a centralized call processing. CUCM Pub/Sub and UnityConn Pub/Sub. We are bringing up a NYC branch and have a few options open to us. (currently we have 1 UCS server in NYC but its not being used for anything) Given best practice deployment models, which is a better deployment ? Option # 1 : Put a LA CUCM Subscriber in NYC which the NYC phones will use to register too but calls will come out of the NYC gateway via the PRI. This option will also include a UnityConn PUB in NYC and a UnityConn Subscriber in LA so that if the UCS server in NYC goes down, voicemail will be uneffected. Option # 2 : Go full distributed call processing, LA is its own Site. NYC is its own site with its own CUCM Pub and Unity Pub. Gateway will have SRST for failover and there will be a NYC UnityConn Sub in LA for voicemail failover what are the pro's and con's of these options ? much appreciated , Thank you
... View more