10-21-2014 01:21 AM - edited 03-14-2019 02:00 PM
Hi to all !
I' am deploying cvp courtesy callback. in my test lab. Call comes to CallbackEntry script, after to BillingQueue but after queue music plays infinitely...
Maximum Estimated wait Time set = 0 in CallbackEntry, Agent logged on in "not ready".
I can't anderstand how to trubleshoot it. VXML application logs and GW Debug does not contain any errors.. Need help .
Regards, Alexey
10-23-2014 07:06 AM
Hi, Abu.
I disabled all sip-profiles, but when INVITE was send, i also didn't see Call Info.
Maybe to try change IOS ?
10-23-2014 06:28 PM
Hi,
If you disable SIP profile, it wont work. You need to add the Call-Info header in a required format. Here is two option you can try.
Option 1: Modify the Call-Info header
voice class sip-profiles 777
request INVITE sip-header Call-Info modify ".*" "X-Cisco-CCBProbe:id:172.32.6.225;loc:lab;trunks:1"
dial-peer voice 1102 voip
description Incoming to CVP
destination-pattern 225T
session protocol sipv2
session target ipv4:172.16.33.76
voice-class codec 1
voice-class sip profiles 777
dtmf-relay rtp-nte h245-signal h245-alphanumeric
no vad
!
Option 2: Remove and add back the Call-Info Header
voice class sip-profiles 776
request INVITE sip-header Call-Info remove
voice class sip-profiles 777
request INVITE sip-header Call-Info add "X-Cisco-CCBProbe:id:172.32.6.225;loc:lab;trunks:1"
dial-peer voice 1105 voip
description Incoming DID for SIP Calls
service cvp-survivability
session protocol sipv2
session target sip-server
incoming called-number .
dtmf-relay rtp-nte
codec g711ulaw
no vad
voice-class sip profiles 776
!
dial-peer voice 1102 voip
description Incoming to CVP
destination-pattern 225T
session protocol sipv2
session target ipv4:172.16.33.76
voice-class codec 1
voice-class sip profiles 777
dtmf-relay rtp-nte h245-signal h245-alphanumeric
no vad
!
Option 2 is better for long term as you would not know if all Incoming calls will have Call-Info header already set or not. If the Call-Info header is set, it will be removed.
Again, run debug ccsip message to confirm that the Call-Info header is set correctly with ccb params when the INVITE goes out to CVP. Unless you've got that working, your CCB wont work. Let me know how it goes.
10-24-2014 12:57 AM
Hi, Abu.
Option 1 i'm testing now, but can't see in sending invite CallInfo
Oct 24 11:43:12.854: //-1/xxxxxxxxxxxx/SIP/Info/sip_profiles_application_modify_remove_header: Unable to get header from stack
If i understand right after survivability service , Call-info header is not set.
Option 2 i used yesterday, but nothing changed.
Why it doesn't adding when we use only ADD function ?
but in logs
//-1/xxxxxxxxxxxx/SIP/Info/sip_profiles_application_change_sip_headers: New header added to the SIP message : X-Cisco-CCBProbe:id:172.32.6.225;loc:lab;trunks:1
Regards, Alexey
10-24-2014 06:19 AM
Hi Alexey
I cant say unless I see complete debug. I think at this point, you better open a TAC case and work with CUBE team to make sure that the INVITE from CUBE to CVP has proper Call-Info header.
Thank you
Abu
02-25-2016 11:19 PM
hi,
We were deploying CCB. Thought of updating this discussion:
When we tested, it was playing back only the queue music.
We checked (monitored) the ICM script and the VXML application status to troubleshoot.
1. We got the error in the activity.log of "CallbackEntry":
Validate_01 - "error.com.cisco.callhandoff.failure"
It points clearly to non configuration of survivability on the ingress gateway.
2. We got the probe error in the activity log:
Validate_01 - Error returned from probe
We discovered that we had mis-typed the param config
param ccb id:172.32.6.225;loc:lab;trunks:1 <= CORRECT
as
param ccb id:172.32.6.225;loc:lab;trunk:1 <=INCORRECT (note missing 's' in 'trunks')
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