The UK's Number One VoIP Resource
This is a discussion on Shang332, A 32 port ATA with cisco callmanager within the uk.telecom.voip forums, part of the Newsgroup Forums category; I have tested Xia308, a 8 ports ATA with cisco callmanager in H.323 and sip, which work fine. Now ...
|
|||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
Welcome to the UKVoIPTalk.com forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
![]() |
| LinkBack | Thread Tools | Display Modes |
|
|||
|
I have tested Xia308, a 8 ports ATA with cisco callmanager in H.323
and sip, which work fine. Now I am test Shang332, an 32 ports ATA with cisco callmanager in h. 323, the h.323 message send from Shang332 is nearly same to Xia308, but the calls were refused by CallManager. I get those 2 calls trace from CCM. Shang332$B!'(B 04/17/2008 13:08:51.995 89.185.71.68 1,100,117,141472.1 Cisco CallManagerCdcc - fill security info to Callinfo SideAsecureStatus = 1, SideBsecureStatus = 1 04/17/2008 13:08:51.995 89.185.71.68 1,100,117,141472.1 Cisco CallManagerCc::wait_CfDataInd, total fie to handle is 0 Xia308$B!'(B 04/16/2008 13:58:17.867 89.185.71.68 1,100,117,135500.1 Cisco CallManagerCdcc - fill security info to Callinfo SideAsecureStatus = 1, SideBsecureStatus = 1 $B!D!D(B 04/16/2008 13:58:17.867 89.185.71.68 1,100,117,135500.1 Cisco CallManagerdecodeFacData::NFE encoding: facId=28 04/16/2008 13:58:17.867 89.185.71.68 1,100,117,135500.1 Cisco CallManagerisCmDestinationPinx::nfe_chosen 04/16/2008 13:58:17.867 89.185.71.68 1,100,117,135500.1 Cisco CallManagerisCmDestinationPinx::destinationEntity is endPINX retVal = 1 04/16/2008 13:58:17.867 89.185.71.68 1,100,117,135500.1 Cisco CallManagerdecodeFacData::CM is the destination: facId=28 04/16/2008 13:58:17.867 89.185.71.68 1,100,117,135500.1 Cisco CallManagerCc::wait_CfDataInd, inserting entry to carryOnResLst, errType is 0 04/16/2008 13:58:17.867 89.185.71.68 1,100,117,135500.1 Cisco CallManagerCc::wait_CfDataInd, invoke id is 1 i = 0 04/16/2008 13:58:17.867 89.185.71.68 1,100,117,135500.1 Cisco CallManagerCc::wait_CfDataInd, total fie to handle is 1 $B!D!D(B I think the key is after get Xia308's setup message $B!$(BCCM go to CallManagerdecodeFacData$B!"(BCallManagerisCmDestinationPinx and calls continue. who can tell me what's the function of those two CallManagerdecodeFacData$B!"(BCallManagerisCmDestinationPinx ? I try to google it, but found nothing. |
|
|||
|
On Thu, 17 Apr 2008 23:38:38 -0700, weedsgrace wrote:
[color=blue] > who can tell me what's the function of those two > CallManagerdecodeFacDataćCallManagerisCmDestinationPinx ? > > I try to google it, but found nothing.[/color] You might have more luck in comp.dcom.sys.cisco. -- <http://ale.cx/> (AIM:troffasky) (UnSoEsNpEaTm@ale.cx) 14:37:06 up 68 days, 21:32, 2 users, load average: 0.03, 0.08, 0.08 Convergence, n: The act of using separate DSL circuits for voice and data |
![]() |
| Thread Tools | |
| Display Modes | |
|
|