Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

cvp courtesy callback

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

19 REPLIES
New Member

I found somthing in

I found somthing in CallbackEntry log, think problem in this.

172.16.33.76.1413816697726.0.CallbackEntry,10/20/2014 18:51:38.413,Validate_01,enter,
172.16.33.76.1413816697726.0.CallbackEntry,10/20/2014 18:51:38.413,Validate_01,custom,Callback_Validate,ELEMENT_ENTRY
172.16.33.76.1413816697726.0.CallbackEntry,10/20/2014 18:51:38.460,Validate_01,custom,Callback_Validate,ELEMENT_ENTRY
172.16.33.76.1413816697726.0.CallbackEntry,10/20/2014 18:51:38.460,Validate_01,element,warning,addXmlBody - Error returned from probe
172.16.33.76.1413816697726.0.CallbackEntry,10/20/2014 18:51:38.460,Validate_01,exit,error

Silver

Hi,For courtesy callback,

Hi,

For courtesy callback, there are lot of dependency of configuration. The error that you've mentioned could happen for multiple configuration error. Can you see if you can access the following link? It has very detailed steps how to configure it. If you can follow step by step, you can make it work.

 

https://techzone.cisco.com/cisco/attachments/cisco/ucc_ucce_cvp@tkb/35/2/Courtesy%20Callback%20quick%20configuration%20steps%201.1.pdf

 

 

 

New Member

Hi, Abu Hadee!Thanks for you

Hi, Abu Hadee!

Thanks for you response.

I read it few times, but can't find error in my config )   I understand right that problrm in GW config?

I'm use  Cisco 2811 (C2800NM-ADVENTERPRISEK9-M), Version 15.1(4)M8

GW IP 172.32.6.225

Call and VXML CVP Server IP 172.16.33.76.

 

 

service cvp-survivability flash:survivability.tcl
  paramspace english index 0
  paramspace english location flash:
  param ccb id:172.32.6.225;loc:lab;trunks:1
  paramspace english english en
  paramspace english prefix en

 

!

service cvp_cc flash:cvp_ccb_vxml.tcl

!

voice class sip-profiles 987
 request INVITE sip-header Call-Info add "X-Cisco-CCBProbe:id:172.32.6.225;loc:lab;trunks:1"

!

dial-peer voice 1101 voip
 description FROM CVP CALLSERVER
 service bootstrap
 incoming called-number 00000000000T
 voice-class sip rel1xx disable
 dtmf-relay rtp-nte h245-signal h245-alphanumeric
 codec g711ulaw
 no vad

!
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

!
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 987
 dtmf-relay rtp-nte h245-signal h245-alphanumeric
 no vad

 

 

 

Silver

Your gateway configuration

Your gateway configuration looks ok to me. But I'm not sure if the SIP message append the CCB Probe properly or not. Can you enable "debug ccsip message" on the CUBE? Once you make the call, then look the SIP INVITE that goes to CVP has a call-info header with the CCB Probe information.

New Member

Yes, i checked it at firstOct

Yes, i checked it at first


Oct 22 13:02:46.081: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:0000000000013@172.32.6.225:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.16.33.76:5060;branch=z9hG4bKjYD65BiOz48Q+vnYBKdW9Q~~42
Max-Forwards: 68
To: <sip:0000000000013@172.32.6.225:5060;transport=tcp>
From: "--CVP_9_0_1_0_0_0_670" <sip:4040@172.16.33.76:5060>;tag=ds1c57b28
Call-ID: 2EB0AE000001000000000029632110AC-141396851168814@172.16.33.76
CSeq: 1 INVITE
Content-Length: 0
Contact: <sip:4040@172.16.33.76:5060;transport=tcp>
Expires: 60
User-Agent: CVP 9.0 (1) Build-670
Call-Info: <sip:172.32.6.225:5060>;purpose=x-cisco-origIP
Remote-Party-ID: "--CVP_9_0_1_0_0_0_670" <sip:4040@172.32.6.225>;party=calling;screen=yes;privacy=off
Date: Wed, 22 Oct 2014 09:02:46 GMT
Min-SE: 1800
Cisco-Guid: 0783330816-0000065536-0000000041-1663111340
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Session-Expires: 1800
X-Cisco-CCBProbe: id:172.32.6.225;loc:lab;trunks:1
Cisco-Gucid: 2EB0AE000001000000000029632110AC
Supported: timer
Supported: resource-priority
Supported: replaces
Supported: sdp-anat
App-Info: <172.16.33.76:8000:8443>

 

Silver

The Call-Info header wasn't

The Call-Info header wasn't added properly.

It should be as follow iin the INVITE message.

Call-Info: X-Cisco-CCBProbe: id:172.32.6.225;loc:lab;trunks:1

The header name is missed. The configuration looks ok, not sure why it is not adding. Can you rewrite the sip profile again? instead of copy, try to use tab to complete the these - request INVITE sip-header Call-Info add

and then type in the rest. Test it again.

 

New Member

I deleted old and created new

I deleted old and created new sip-profile, but info added in the and of frame:


Oct 22 14:41:20.569: //61/F3B577000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:2255@172.16.33.76:5060 SIP/2.0
Via: SIP/2.0/UDP 172.32.6.225:5060;branch=z9hG4bK29184E
Remote-Party-ID: "--CVP_9_0_1_0_0_0_670" <sip:4040@172.32.6.225>;party=calling;screen=yes;privacy=off
From: "--CVP_9_0_1_0_0_0_670" <sip:4040@95.211.216.165>;tag=CCE6F8-19AE
To: <sip:2255@172.16.33.76>
Date: Wed, 22 Oct 2014 10:41:20 GMT
Call-ID: CB729EA4-590E11E4-804EA700-96706A01@172.32.6.225
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 4088755968-0000065536-0000000042-1663111340
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1413974480
Contact: <sip:4040@172.32.6.225:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires:  1800
Content-Length: 0
X-Cisco-CCBProbe:id:172.32.6.225;loc:lab;trunks

 

Why it may happen?

 

 

 

Silver

Its not a problem to be added

Its not a problem to be added at the end. But the header name needs to be added as well. Can you send me the complete configuration of the CUBE? If you are only making test call and no other call in the gateway, please collect "debug ccsip all" and let me verify it.

New Member

Config and trace in attach

Config and trace in attach

Silver

Sorry, I need "debug ccsip

Sorry, I need "debug ccsip all" to see why the sip profile isn't taking effect properly. can you collect again please with the above debug? make sure you do not have any other call while you have the above debug on. What version of IOS you are running?

New Member

Ok. Enabled all sip debugging

Ok. Enabled all sip debugging. Trace in attach.   

Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version 15.1(4)M8, RELEASE SOFTWARE (fc2)

 

Silver

Your Incoming INVITE has Call

Your Incoming INVITE has Call-Info header already set. That is why, it messed up the CCB header addition.

 

From the SIP message, I can see the INVITE is coming from CUCM. Are you making the call from an IP Phone? You need to either turn off the Call-Info header from CUCM, or modify the SIP Profile such that, it removes the incoming header information and add what ever you wanted to add.


 

New Member

I couldn't find a way how

I couldn't find a way how turn off Call-Info header from CUCM.

I created second sip-profile   request INVITE sip-header Call-Info REMOVE

and apply it to inbound Dial-peer, but changed nothing.

Why in recieved INVITE i can see word "Call-Info", but in sent INVITE "Call-Info" missing?  (

But it was added in the end (but you sayed it no problem) 

Line 391: Oct 22 18:45:46.947: //-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

Maybe problem in something other?

Regards, Alexey

 

Silver

Hi Alexy,The header is

Hi Alexy,

The header is malformed. The Header name is not present when the INVITE is sent. The header should look like

 

Call-Info: X-Cisco-CCBProbe:id:172.32.6.225;loc:lab;trunks:1

If the header is correctly formed, then the order of header message is not important.

You have couple of option if you can not stop it from CUCM to send. You can configure another SIP Profile in the inbound dilapeer to remove the Call-Info header, then it will be added by the sip profile outbound dialpeer. The 2nd option is just to use one SIP profile on outbound, so you need to modify the Call-Info header, replace everything with the above. I do not have any test bed to test the sip profile. For you, it will be easy to use the first option where you remove it first which will be simple. But in any case, if you run "debug ccsip message", you must the "Call-Info" header correctly formed, otherwise, ccb will always fail.

 

Abu

New Member

Hi, Abu.I disabled all sip

Hi, Abu.

I disabled all sip-profiles, but when INVITE was send, i  also didn't see Call Info.

Maybe to try change IOS ?

 

 

Silver

Hi,If you disable SIP profile

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.

New Member

Hi, Abu. Option 1 i'm testing

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

 

Silver

Hi Alexey I cant say unless I

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

 

New Member

hi,

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')

642
Views
4
Helpful
19
Replies
CreatePlease login to create content