05-08-2009 12:27 AM - edited 03-14-2019 04:03 AM
Hi,
ICM 7.5
CVP 7.0
VXML5350
CCM 6.1.3
Gatekeeper (GUP)
My setup is not able to land call on agent phone, the phone goes to reserved state but is not able to receive call.
I assume that the ICM is reserving the call as it is showing the Label (agent phone line number) in router log but the CVP is not able to get the lable or not sending it to Gatekeeper.
As soon as the Agent becomes ready the system drops the call.
Here is log from CVP.
7:12:29 Trace: 00000012: CALLFLOW: IP transfer - Agent hung up : DNIS = 7001234567152 : GUID = 2F9064F80304001F20345DD2A3A0591F : CID = 9FE79F26397F11DE83D10022915807EC
17:12:29 Trace: 00000012: CALLFLOW: Call ended : DNIS = 7001234567152 : GUID = 2F9064F80304001F20345DD2A3A0591F : CID = 9FE79F26397F11DE83D10022915807EC
17:12:29 Trace: 00000011: CALLFLOW: Call successfully established (slow start) : DNIS = 8881 : CID = 9FE79F26397F11DE83D10022915807EC
17:12:31 Trace: 00000011: CALLFLOW: Disconnecting caller because agent hung up. : DNIS = 8881 : CID =
The disconnect error is like.
17:22:46 Trace: DEVICE_TARGET_ABORT_IND message received from Peripheral(5000) CRSCallID(Date 149144 ,ID 696), NetworkTarget(5000),MRDomain(1), Agent(5009).
The Gatekeeper is not showing the request for the Label (agent phone number).
Here is debug from gatekeeper.
May 8 08:41:02.696: gk_rassrv_arq: arqp=0x447C5298, crv=0x320, answerCall=0
May 8 08:41:02.696: gk_dns_query: No Name servers
May 8 08:41:02.696: rassrv_get_addrinfo: (8881) Tech-prefix match failed.
May 8 08:41:02.696: rassrv_get_addrinfo: (8881) Matched zone prefix 88 and remainder 81
May 8 08:41:02.696: rassrv_arq_select_viazone: about to check the source side, src_zonep=0x45932540
May 8 08:41:02.696: rassrv_arq_select_viazone: matched zone is SIDEA, and z_invianamelen=0
May 8 08:41:02.696: rassrv_arq_select_viazone: about to check the destination side, dst_zonep=0x45932540
May 8 08:41:02.700: rassrv_arq_select_viazone: matched zone is SIDEA, and z_outvianamelen=0
May 8 08:41:02.904: gk_rassrv_arq: arqp=0x447C5298, crv=0x3A90, answerCall=1
May 8 08:41:02.908: gk_rassrv_irr: irrp=0x447C5298, from 10.20.63.100:51859
May 8 08:41:02.916: gk_rassrv_brq: state = 0xF
May 8 08:41:02.916: gk_rassrv_brq: brqp=0x45254CE0, crv=0x3A90, bandWidth=1280
May 8 08:41:02.928: gk_rassrv_arq: arqp=0x447C5298, crv=0x3A91, answerCall=0
May 8 08:41:02.928: gk_dns_query: No Name servers
May 8 08:41:02.928: rassrv_get_addrinfo: (70012345671049) Tech-prefix match failed.
May 8 08:41:02.928: rassrv_get_addrinfo: (70012345671049) Matched zone prefix 7001234567 and remainder 1049
May 8 08:41:02.928: rassrv_arq_select_viazone: about to check the source side, src_zonep=0x45932540
May 8 08:41:02.928: rassrv_arq_select_viazone: matched zone is SIDEA, and z_invianamelen=0
May 8 08:41:02.928: rassrv_arq_select_viazone: about to check the destination side, dst_zonep=0x45932540
May 8 08:41:02.928: rassrv_arq_select_viazone: matched zone is SIDEA, and z_outvianamelen=0
May 8 08:41:02.928: gk_rassrv_brq: state = 0xF
May 8 08:41:02.928: gk_rassrv_brq: brqp=0x45254CE0, crv=0x320, bandWidth=0
May 8 08:41:02.932: gk_rassrv_arq: arqp=0x45A0806C, crv=0x1E7, answerCall=1
May 8 08:41:02.944: gk_rassrv_irr: irrp=0x447C58B8, from 10.20.63.101:56715
May 8 08:41:02.948: gk_rassrv_brq: state = 0xF
May 8 08:41:02.948: gk_rassrv_brq: brqp=0x45254CE0, crv=0x320, bandWidth=1280
May 8 08:41:02.952: gk_rassrv_brq: state = 0xF
May 8 08:41:02.952: gk_rassrv_brq: brqp=0x45254CE0, crv=0x3A90, bandWidth=1280
May 8 08:41:02.952: gk_rassrv_brq: state = 0xF
May 8 08:41:02.952: gk_rassrv_brq: brqp=0x45254CE0, crv=0x3A91, bandWidth=1280
May 8 08:41:05.224: gk_process_read_event: Recd event from altgk
05-11-2009 11:27 AM
Sandeep, not to worry. No one in their right mind would use three digit extensions with CVP.
I also think 4 is too small (we have been caught out when customers insisted on 4 digit extensions, despite our objections).
I want at least 5 for single sites.
For multi-site deployments within a country, I think you need 7 or 8.
For international deployments, we use 8 or 9.
Regards,
Geoff
05-11-2009 09:36 PM
thanks geoff,
I would definitely keep this in mind for next designs but i don't understand why it doesn't work with 3 digits.
Our setup is having 200-250 agents and can go maximum to 350 in coming 5 years.
As the customer was already using other product he wanted to keep the agent extensions same.
We are able to see some errors in CVP i guess this thing is hard-coded.
05-12-2009 12:34 AM
Sandeep,
"As the customer was already using other product he wanted to keep the agent extensions same."
That's often the reason, but it does not work out very well to have such a limited dial plan.
If all agents have to enter (say) "74xxx" where xxx is the old three digit extension, then they don't really have to remember anything special, as the prefix is always "74".
But now you have a 5 digit dial plan, and that's going to be much more successful and expandable.
Regards,
Geoff
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide