Re: Cisco CVP Standalone Outbound

Muhammed Ashiq · ‎05-12-2020

Dears,

We are trying to implement Cisco CVP Standalone Outbound as described by Engineer Mr.Paul Tindal.

https://twitter.com/tindallpaul/status/919638559702822912

Below are the setup we are using,

Cisco PCCE 12.0

Cisco CVP 12.0

Cisco VVB 12.0

Voice Gateway 29XX

Did anyone implemented this setup.Need help in VVB Configuartion.

ptindall · ‎05-13-2020

There's not really much to do differently on the VVB.

Start with the original non-VVB materials on Devnet CVP samples to understand how it works and for a quick-start outbound DB based dialing list if you need it.
Then read and follow the specific notes at https://app.box.com/s/qp9sbeh0zcf7z3bp2xb2jop6fprox9ma for using the VVB edition.
Add the VVB compatible version of the MakeCall custom element to CVP Studio and run-time.
Build and deploy your outbound test Studio app that uses the MakeCall element.
Configure the inbound trigger DN on VVB admin to map to the CVP Standalone application you just deployed.
Start the outbound app on the gateway/CUBE as normal.
Use "deb voip appl script" for diagnostics.

Paul

Muhammed Ashiq · ‎05-13-2020

Dear Paul,

thanks for the response,we have followed the steps .Unable to start Outbound dialing.

We are getting following from the Voice gateway,

May 13 09:55:09.869: //-1//TCL :EE3F4BC6B0000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: started poll timer

May 13 09:55:24.869: //-1//TCL :EE3F4BC6B0000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: making call to poll CVP VXML application at <7788000>

May 13 09:55:24.913: //-1//TCL :EE3F4BC6B0000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: call to poll CVP VXML outbound application established

May 13 09:57:25.078: //-1//TCL :EE3F4BC6B0000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: poll call to CVP VXML application disconnected, status di_016

From the VXML application activity logs,

Makecall_01,element,error,error.unsupported.objectname: classid=com.cisco.callhandoff service=cvp_obcallreq.

Thanks.

ptindall · ‎05-13-2020

That is either the non-VVB MakeCall element you're using or the correct VVB compatible one that hasn't identified the browser type. Post the activity log up to and including the MakeCall.

Muhammed Ashiq · ‎05-14-2020

We are going with the old Setup now ie,VXML gateway mode. where will be the configuration is missed.

ptindall · ‎05-14-2020

The warnings you highlighted can be ignored. These are local params that haven't been assigned to a namespace.

Muhammed Ashiq · ‎05-14-2020

Below are the logs we are getting.

We are having both VXML GW and Voice GW in one.

CVP Standalone

DNIS=2001

Clid=2255

No dialing happening.

SIDVGW01#debug voip application script
voip application script debugging is on
SIDVGW01#
May 15 00:18:20.874: //-1//TCL :EE22BE1230000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: poll call to CVP VXML application disconnected, status di_102
May 15 00:18:20.874: //-1//TCL :EE22BE1230000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: started poll timer
May 15 00:18:35.874: //-1//TCL :EE22BE1230000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: making call to poll CVP VXML application at <7788000>
May 15 00:18:35.882: //90//TCL :/tcl_PutsObjCmd:
TCL CVP: ******* Call arrived with ANI=sip:10.1.47.222, DNIS=7788000, CALLID=73BF1C77957811EA807ED596213E299E ******** CallID = 73BF1C77957811EA807ED596213E299E
May 15 00:18:35.910: //-1//TCL :EE22BE1230000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: call to poll CVP VXML outbound application established
May 15 00:18:35.962: //90//TCL :/tcl_PutsObjCmd: ******* CVP_OBCALLREQ: assumed control of call with argument: <dnis=2001 cli=2255 rna=30 id=73BF1C77957811EA807ED596213E299E uui="234273843">
May 15 00:18:35.962: //90//TCL :/tcl_PutsObjCmd: ******* CVP_OBCALLREQ: sent dialer record to CVP_OUTBOUND.TCL, waiting for call outcome ...
May 15 00:18:53.902: //-1//TCL :EE22BE1230000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: poll call to CVP VXML application disconnected, status di_102
May 15 00:18:53.902: //-1//TCL :EE22BE1230000:/tcl_PutsObjCmd: ******* CVP_OUTBOUND: started poll timer

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Activity Log
=====================================================================
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,newcall,
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,ani,sip:10.1.47.222
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,areacode,NA
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,exchange,NA
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,dnis,sip:7788000@10.1.47.222:5060
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,uui,NA
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,iidigits,NA
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,parameter,callid=73BF1C77957811EA807ED596213E299E
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,parameter,tclversion=CVP_12_0_1_0_0_0_229
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,parameter,vxmlversion=CVP_12_0_1_0_0_0_229
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,,start,parameter,var1=7788000
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.866,GetParam,enter,
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.915,GetParam,exit,done
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:35.915,Makecall_01,enter,
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:53.876,Makecall_01,exit,
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:53.876,,end,how,hangup
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:53.876,,end,result,normal
10.1.47.183.1589501915866.61.outbound,05/15/2020 03:18:53.876,,end,duration,18

ptindall · ‎05-15-2020

A SIP INFO message should be sent between CVP_OBCALLREQ and CVP_OUTBOUND. As the trace shows one never arrives, check you have "signalling forward unconditional" enabled globally under voice service voip or at dial-peer level for the polling call. Turn on "deb ccsip mess" to check the SIP INFO is sent.

Paul

Muhammed Ashiq · ‎05-15-2020

Unconditional forwarding is enabled in globally already.

Please find the below debug sip info.Thanks.

May 15 12:48:23.768: //1594/329E796188C7/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.1.47.82:58800;branch=z9hG4bK-d8754z-ac59dd783756314a-1---d8754z-;rport
From: <sip:sipping@10.1.47.82>;tag=6f49c068
To: <sip:10.1.47.222>;tag=34C000-1149
Date: Fri, 15 May 2020 12:48:23 GMT
Call-ID: 543e523b-f62f603b-74440765-c872b952
Server: Cisco-SIPGateway/IOS-15.7.3.M3
CSeq: 1 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 367

v=0
o=CiscoSystemsSIP-GW-UserAgent 8246 7752 IN IP4 10.1.47.222
s=SIP Call
c=IN IP4 10.1.47.222
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15
c=IN IP4 10.1.47.222
m=image 0 udptl t38
c=IN IP4 10.1.47.222
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

May 15 12:48:24.704: //1589/286E6DEC88BB/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:10.1.47.222:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.47.222:5060;branch=z9hG4bK24B1591
From: <sip:7788000@10.1.47.222>;tag=347D44-1546
To: <sip:10.1.47.222>;tag=347D3C-170D
Date: Fri, 15 May 2020 12:48:06 GMT
Call-ID: 286E6DEC-95E111EA-88BEA58E-D28994B@10.1.47.222
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M3
Max-Forwards: 70
Timestamp: 1589546904
CSeq: 102 BYE
Reason: Q.850;cause=102
P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0,JI=0,LA=0,DU=18
Session-ID: 3200c6a3733654b59f4bc1c952dfb414;remote=f84d1c0045e05f2ebfef14779aae6963
Content-Length: 0

May 15 12:48:24.704: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:10.1.47.222:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.47.222:5060;branch=z9hG4bK24B1591
From: <sip:7788000@10.1.47.222>;tag=347D44-1546
To: <sip:10.1.47.222>;tag=347D3C-170D
Date: Fri, 15 May 2020 12:48:06 GMT
Call-ID: 286E6DEC-95E111EA-88BEA58E-D28994B@10.1.47.222
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M3
Max-Forwards: 70
Timestamp: 1589546904
CSeq: 102 BYE
Reason: Q.850;cause=102
P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0,JI=0,LA=0,DU=18
Session-ID: 3200c6a3733654b59f4bc1c952dfb414;remote=f84d1c0045e05f2ebfef14779aae6963
Content-Length: 0

May 15 12:48:24.704: //1588/286E6DEC88BB/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.1.47.222:5060;branch=z9hG4bK24B1591
From: <sip:7788000@10.1.47.222>;tag=347D44-1546
To: <sip:10.1.47.222>;tag=347D3C-170D
Date: Fri, 15 May 2020 12:48:24 GMT
Call-ID: 286E6DEC-95E111EA-88BEA58E-D28994B@10.1.47.222
Server: Cisco-SIPGateway/IOS-15.7.3.M3
Timestamp: 1589546904
CSeq: 102 BYE
Reason: Q.850;cause=102
P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0,JI=0,LA=0,DU=18
Session-ID: f84d1c0045e05f2ebfef14779aae6963;remote=3200c6a3733654b59f4bc1c952dfb414
Content-Length: 0

May 15 12:48:24.708: //1589/286E6DEC88BB/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.1.47.222:5060;branch=z9hG4bK24B1591
From: <sip:7788000@10.1.47.222>;tag=347D44-1546
To: <sip:10.1.47.222>;tag=347D3C-170D
Date: Fri, 15 May 2020 12:48:24 GMT
Call-ID: 286E6DEC-95E111EA-88BEA58E-D28994B@10.1.47.222
Server: Cisco-SIPGateway/IOS-15.7.3.M3
Timestamp: 1589546904
CSeq: 102 BYE
Reason: Q.850;cause=102
P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0,JI=0,LA=0,DU=18
Session-ID: f84d1c0045e05f2ebfef14779aae6963;remote=3200c6a3733654b59f4bc1c952dfb414
Content-Length: 0

May 15 12:48:28.764: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.1.47.222 SIP/2.0
Via: SIP/2.0/UDP 10.1.47.82:58800;branch=z9hG4bK-d8754z-ac234429e008af2a-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:sipping@10.1.47.82:58800>
To: <sip:10.1.47.222>
From: <sip:sipping@10.1.47.82>;tag=bb740f16
Call-ID: 874b200e-7951673b-566a1e4c-40204e60
CSeq: 1 OPTIONS
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, NOTIFY, PRACK, REFER, NOTIFY, OPTIONS
Supported: timer, resource-priority, replaces
Content-Length: 0

May 15 12:48:28.768: //1595/359A06A188C8/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.1.47.82:58800;branch=z9hG4bK-d8754z-ac234429e008af2a-1---d8754z-;rport
From: <sip:sipping@10.1.47.82>;tag=bb740f16
To: <sip:10.1.47.222>;tag=34D38C-19BB
Date: Fri, 15 May 2020 12:48:28 GMT
Call-ID: 874b200e-7951673b-566a1e4c-40204e60
Server: Cisco-SIPGateway/IOS-15.7.3.M3
CSeq: 1 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 367

v=0
o=CiscoSystemsSIP-GW-UserAgent 1263 1597 IN IP4 10.1.47.222
s=SIP Call
c=IN IP4 10.1.47.222
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15
c=IN IP4 10.1.47.222
m=image 0 udptl t38
c=IN IP4 10.1.47.222
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

May 15 12:48:28.944: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:

no deb ccsip mess
SIP Call messages tracing is disabled
SIDVGW01#
May 15 12:48:33.828: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.1.47.222 SIP/2.0
Via: SIP/2.0/UDP 10.1.47.82:58800;branch=z9hG4bK-d8754z-2e6f47772932a520-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:sipping@10.1.47.82:58800>
To: <sip:10.1.47.222>
From: <sip:sipping@10.1.47.82>;tag=e74cd052
Call-ID: e07b6d01-4e0f6342-1a08d870-87129b06
CSeq: 1 OPTIONS
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, NOTIFY, PRACK, REFER, NOTIFY, OPTIONS
Supported: timer, resource-priority, replaces
Content-Length: 0

May 15 12:48:33.832: //1596/389E1FDB88C9/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.1.47.82:58800;branch=z9hG4bK-d8754z-2e6f47772932a520-1---d8754z-;rport
From: <sip:sipping@10.1.47.82>;tag=e74cd052
To: <sip:10.1.47.222>;tag=34E754-2432
Date: Fri, 15 May 2020 12:48:33 GMT
Call-ID: e07b6d01-4e0f6342-1a08d870-87129b06
Server: Cisco-SIPGateway/IOS-15.7.3.M3
CSeq: 1 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 367

v=0
o=CiscoSystemsSIP-GW-UserAgent 5359 9699 IN IP4 10.1.47.222
s=SIP Call
c=IN IP4 10.1.47.222
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15
c=IN IP4 10.1.47.222
m=image 0 udptl t38
c=IN IP4 10.1.47.222
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

ptindall · ‎05-15-2020

Not much information as it stands as it doesn't even have the original SIP INVITE and there's no SIP INFO. Send me a full trace with "deb voip app script", "deb voip app tcl" and "deb ccsip mess" covering the full call scenario.

Muhammed Ashiq · ‎05-15-2020

Attaching file with debug enabled.

ptindall · ‎05-15-2020

The polling leg is receiving the SIP INFO containing the dialing record but the cvp_outbound TCL application isn't seeing it. Check your gateway SIP config to make sure there's nothing blocking signalling.

Muhammed Ashiq · ‎11-24-2020

Hi Mr.Paul,

Can we use the same TCL script for invoking multiple applications ?

Let's say we have two VXML applications to be run on this setup.

ptindall · ‎11-24-2020

Using it as published, without any modifications, it's built to make calls to a single number which in turn maps to a single Studio app. To trigger an additional Studio app in parallel, you would have to run another instance of the outbound TCL that uses a different polling number. The Studio app that actually does the call handling once the customer answers can be changed at the app level by passing control to another app via subdialog or app transfer elements. In that case you'd only need to use a single TCL instance.

So, it really depends on the precise use case. If the requirement is to use different scripts containing the MakeCall element in parallel then multiple TCL instances would be needed. If the multiple handling cases can be worked into a single Studio app then only a single TCL instance would be required.

Other possible approaches would be to modify the TCL to cycle through a list of polling numbers, or use a weighted list etc. I'm not entirely convinced it's worth the additional complexity when you can always just run multiple instances to achieve the same thing.

Muhammed Ashiq · ‎12-20-2021

Hi Mr.Paul,

If we want to use multiple instance of what are the parameters to be changed ?

ex:-

!

application

service cvp_outbound_1 flash:cvp_outbound.tcl

.............

!

application

service cvp_outbound_2 flash:cvp_outbound.tcl

.............

!

session

start ob cvp_outbound_1

!

session

start ob cvp_outbound_2

!

Is this would be enough ?