cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1842
Views
0
Helpful
22
Replies
Highlighted
Rising star

Re: Courtesy Callback Configuration

For the benefit of the group, can you share what had to be added/changed?

Highlighted
Beginner

Re: Courtesy Callback Configuration

Sure, it was mis-configuration on gateway as i am not familiar with gateway conf.

Below is feedback from TAC engineer:

Al calls on gateway have incoming dial-peer and outgoing dial-peer.

If incoming dial-peer is not specified – gw uses default inbound dial-peer.

But for CCB you need to configure service. Service is configured only on incoming dial-peer.

So you need specify incoming dial-peer for called number 999 (incoming called-number 999).

This means that all calls with called number 999 will be used this dial-peer as incoming.

 

dial-peer voice 201 pots

trunkgroup XXX

incoming called-number ^6105$

service cvp-survivability

direct-inward-dial

 

View solution in original post

Highlighted
Beginner

Re: Courtesy Callback Configuration

what was that missed config on ingress?

Highlighted
Beginner

Re: Courtesy Callback Configuration

ramimakram stated that there was no incoming dial-peer configured, as such the call would hit default incoming dial-peer 0.

 

The survivability service needs to be configured on an incoming dial-peer, so one needed to be created.

Highlighted
Beginner

Re: Courtesy Callback Configuration

Hi,

 

I'm having the same issue on a CVP 11.0 installation. My ICM script does have set the user.CourtesyCallbackEnabled set to 1. The difference is that my CVP script is called IVRCustomCallBack. In the logs of my CVP Script IVRCustomCallBack none of the call back parameters are shown:

 

192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,newcall,
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,ani,4167356729
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,areacode,416
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,exchange,735
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,dnis,5817
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,uui,NA
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,iidigits,NA
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,parameter,ani=4167356729
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,parameter,qname=billing
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,parameter,callid=6C34EA3431CA11E8A898AD655FB95A71
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,parameter,queueapp=BillingQueue
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,parameter,_dnis=5817
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,parameter,ewt=150
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,,start,parameter,_ani=4167356729
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.314,CVP Subdialog Start_01,enter,
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.377,CVP Subdialog Start_01,exit,done
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.377,Enter Queue_01,enter,
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.377,Enter Queue_01,custom,Callback_Enter_Queue,ELEMENT_ENTRY
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.377,Enter Queue_01,element,warning,Could not retrieve "_ccbServlet". Please check your configuration.
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.377,Enter Queue_01,custom,Callback_Enter_Queue,ELEMENT_EXIT
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.377,Enter Queue_01,exit,error
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.377,PlayErrorAudio1,enter,
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.381,PlayErrorAudio1,interaction,audio_group,initial_audio_group
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.393,PlayErrorAudio1,exit,done
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.393,Get Status_01,enter,
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.393,Get Status_01,custom,Callback_Get_Status,ELEMENT_ENTRY
192.168.32.177.1522247010314.0.IVRCustomCallBackEntry,03/28/2018 10:23:30.393,Get Status_01,element,warning,Could not retrieve "_ccbServlet". Please check your configuration.

 

CVP reporting server is up and runing as well as the Call Servers. Any help is appreciated.

 

Thanks.

 

Carlos Trivino

Highlighted
Advocate

Re: Courtesy Callback Configuration

Well that error about the ccbServlet not running is disturbing. Does this work for you?

 

http://<REPORTING_SERVER>:8000/cvp/CallbackServlet?method=Diag

 

Regards,

Geoff

 

Highlighted
Beginner

Re: Courtesy Callback Configuration

CallBackServlet.JPG

 

Hi Geoff,

 

Yes it does. Here is the screen shot:

 

 

Highlighted
Beginner

Re: Courtesy Callback Configuration

It was mis-configuration on gateway as i am not familiar with gateway conf. Please check above comment marked as solution