I have a bit of a complexed design.
Call manager 6 is configured as centralised with gateways at mutiple sites. Some sites have extensions of the call managers using voip phones while other sites that already have their pbx connect to the call manager using the router over a t1 pri digital trunk. The gateway is configured using h323 to the call manager.
I am having this issue when calls from one site with a legacy pbx is dialling a number for another legacy pbx the user is getting the prompt that "call cant be completed". The route patterns is correct and calls can be made from the legacy pbx to sites with extensions off the call manager.
Will this be a codec issue? I am seeing the digits coming across from the legacy pbx to gateway and they are correct. The only thing is that this set of digits were translated since the user couldnt send digits according to a standard.Looking at the debugs the correct digits are being sent to call manager.
In my case the user is doing the following
user calling number (55221300)-->legacy pbx (calling number 5221300)-->t1 pri-->site A router-->translated to 85221300-->call manager-->route pattern-->SiteB router (1300)-->customer pbx-->phone(1300) rings.
If the user dials an extension of the call manager the calls is successful
user calling number (55202900)-->legacy pbx (calling number 5202900)-->t1 pri-->site A router-->translated to 85202900-->call manager-->translation pattern 5202900-->voip phone rings.
Calls to the site legacy pbx are successful from a voip phone, i still have to verify from site B.
You are right about the number which is passed to CCM, it is indeed "85221300"
// From the setup.
05/09/2012 13:30:25.602 CCM|In Message -- H225SetupMsg -- Protocol= H225Protocol|
05/09/2012 13:30:25.602 CCM|Ie - H225BearerCapabilityIe -- IEData= 04 03 80 90 A3 |
05/09/2012 13:30:25.602 CCM|Ie - H225CallingPartyIe -- IEData= 6C 06 09 80 32 31 36 32 |
05/09/2012 13:30:25.602 CCM|Ie - Q931CalledPartyIe -- IEData= 70 09 80 38 35 32 32 31 33 30 30 |
// But during DA the 8 is stripped, and rest of the digits are sent. It cannot be any translation-pattern issue, as in the setup, we do see the correct digits and it didnt even pass the Digit analysis results. So GW setting is changing it. Only place I can think of is "significant digits".
05/09/2012 13:30:25.611 CCM|H225Cdpc::getDefCcSetupInd Overlapflag 1 sendingComplete 152|
05/09/2012 13:30:25.611 CCM|H225Cdpc - before parsing IVRDN. cdpn=5221300 cgpn=2162 rdn=|
05/09/2012 13:30:25.612 CCM|Cdcc - (0000820) - storeDchanCrp - secure capability on side 0 is (1,0)|
05/09/2012 13:30:25.612 CCM|Cdcc::preliminaryProcessCcSetupInd: precLvl=5|
05/09/2012 13:30:25.612 CCM|Digit Analysis: wait_DaReq: Matching Legacy Numeric, digits=5221300|
05/09/2012 13:30:25.613 CCM|Digit analysis: wait_DaReq - cepn= BlockFlag=|<CLID::GoRTTCluster>
05/09/2012 13:30:25.613 CCM|Digit Analysis: getDaRes - voiceMailCallingSearchSpace=|
// I am suspecting the below reason, I think you have significant digits misconfigured. Can you change it "all". Save the configuration, and reset the gateway and test the call. Make sure to have Partition of RP 85221300 associated to Incoming CSS of H323 GW.
In the Device--Gateway(h323)----> Call Routing Information - Inbound Calls---->Significant digits