cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Cisco Community Designated VIP Class of 2020

outbound_dialing_in_CVP Standalone problem

216
Views
0
Helpful
0
Comments
This document was generated from CDN thread

Created by: CLAUDIO RIVAS on 22-08-2011 08:10:26 PM
Hi,
 
Currently i'm trying to run a CVP Standalone 7.0(2) outbound_dialing_in_CVP application, but seems i have issues on the call to the cvp_dialer.tcl script, the attempts to dial the phone numbers are exausted every time i've tryied.
 
Here is a portion of my configuration:
 
voice service voip
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 allow-connections sip to sip
 fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none
 sip
  bind control source-interface GigabitEthernet0/0
  bind media source-interface GigabitEthernet0/0
  rel1xx disable
  header-passing
!
!
!
voice translation-rule 1
 --More--          rule 1 /987654/ //
!
!
voice translation-profile block
 translate called 1
!
!
!
application
 service cvp_outbound flash:cvp_outbound.tcl
  param cvp-ob-vxml-dest 7788000
  param cvp-ob-poll-interval 15
 !
 service new-call flash:bootstrap.vxml
  paramspace english language en
  paramspace english index 0
  paramspace english location flash
  paramspace english prefix en
 !
 service cvpdialer flash:cvp_dialer.tcl
 !
 service cvp-survivability flash:survivability.tcl
  paramspace english index 0
 --More--           paramspace english language en
  paramspace english location flash
  paramspace english prefix en
 !
 service CVPSelfService flash:CVPSelfServiceBootstrap.vxml
  paramspace english language en
  paramspace english index 0
  paramspace english location flash
  paramspace english prefix en
 !
 service cvp_obcallreq flash:cvp_obcallreq.tcl
 !
 service ringtone flash:ringtone.tcl
  paramspace english language en
  paramspace english index 0
  paramspace english location flash
  paramspace english prefix en
 !
 service sua flash:CVPSelfService.tcl
  param CVPBackupVXMLServer 10.120.44.8
  param CVPSelfService-port 7000
  param CVPSelfService-app sua
  param CVPPrimaryVXMLServer 10.120.44.8
 --More--          !
 service cvperror flash:cvperror.tcl
  paramspace english language en
  paramspace english index 0
  paramspace english location flash
  paramspace english prefix en
 !
 service outbound flash:CVPSelfService.tcl
  param CVPSelfService-app outbound
  param CVPSelfService-port 7000
  param CVPPrimaryVXMLServer Z.Z.Z.Z ------ i've placed here my CVP VXML Standalone Server 
  param CVPBackupVXMLServer Y.Y.Y.Y ------ i've placed here my secondary CVP VXML Standalone Server
 !
 service handoff flash:handoff.tcl
  paramspace english index 0
  paramspace english language en
  paramspace english location flash
  paramspace english prefix enexit
 !
 service bootstrap flash:bootstrap.tcl
  paramspace english language en
  paramspace english index 0
  paramspace english location flash
 --More--           paramspace english prefix en
 !
 session
  start ob cvp_outbound
 !
!
dial-peer voice 987654 voip
 description Blocks ulaw
 --More--          translation-profile incoming block
 incoming called-number 987654
 ip qos dscp cs3 signaling
 no vad
!
dial-peer voice 44000 voip
 description to CallManager Ext 4xxxx
 destination-pattern 4....
 session protocol sipv2
 session target ipv4:X.X.X.X -----I'VE PLACED HERE THE IP ADDRESS OF MY CUCM AND ITS WORKING FINE
 dtmf-relay rtp-nte
 codec g711ulaw
!
dial-peer voice 7780000 voip
 max-conn 23
 destination-pattern 778....
 session protocol sipv2
 session target ipv4: M.M.M.M --------- THIS HAVE MY VXML/EGRESS GATEWAY
 dtmf-relay rtp-nte
 codec g711ulaw
 no vad
!
dial-peer voice 7788000 voip
 --More--          service outbound
 max-conn 10
 incoming called-number 7788000
 dtmf-relay rtp-nte
 codec g711ulaw
 no vad
!
 
 
I've noticed that on the database on every try it does to attempt to place the outbound call it returns a reason code "dialer_resp_timeout".
If you'd like, there is some logfiles attached.
 
Best Regards,
 

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: Paul Tindall on 22-08-2011 08:56:39 PM
Can you get a trace on the gateway with "deb ccsip mess" turned on so we can see the SIP INFO messages that carry the dialer request/response between the two TCL sessions.   Looks like it's sent but I don't see any logging at the other end that indicates it was received.   The VXML application end hits a 300 sec default timeout when the dialer process hasn't responded with a call outcome.

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: CLAUDIO RIVAS on 22-08-2011 09:50:05 PM
Hi Paul,

Thank you for your interest, i've attached the syslog file whith the deb ccsip mess debug enabled. I think i need a review with a big cup of coffee besides.

Regards,

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: Paul Tindall on 23-08-2011 05:36:55 AM
Claudio,
I don't see an attachment.   If you're doing another trace then for now just set the following to make it a bit clearer:
deb voip appl script
deb voip appl tcl
deb voip appl stat
deb ccsip mess

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: CLAUDIO RIVAS on 23-08-2011 12:01:46 PM
Hi Paul,
 
I've taked the logs you comment for a cleaner reading.
 
Regards,

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: Paul Tindall on 23-08-2011 07:34:33 PM
The cvp_outbound.tcl session isn't receiving the dialer directive via a SIP INFO message that should be sent sent from cvp_obcallreq.tcl as a result of executing the Makecall custom element.  The SIP INFO content is sent as GTD payload so configure "signaling forward unconditional" under voice service voip or if you prefer, locally on the CVP outbound dial peers handling your polling number.

Paul

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: CLAUDIO RIVAS on 23-08-2011 08:34:06 PM
Thank you very much Paul,

For this time seems the call is not stablished at all, the phone rings form an unknown source and i can answer, but no audio is on the call and seems on VXML Server Activity logs call is getting terminated once i hang up but is not falling into the steps to write the result to the database.

So my dial peer configuration looks as follows

dial-peer voice 7788000 voip
service outbound
max-conn 10
signaling forward unconditional
incoming called-number 7788000
dtmf-relay rtp-nte
codec g711ulaw
no vad

I'm without options till now, but a ring is a step forward to keep this script running, i appreciate your help.

Regards,

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: CLAUDIO RIVAS on 23-08-2011 11:08:02 PM
Paul,

I've placed the command on the voice service voip and complete the call.
My question is, how is the cvp_dialer invoked?
What do you think about subsequent transfers after the outbound call is stablished?

Regards,
Claudio.

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: Paul Tindall on 24-08-2011 05:00:38 AM
If you don't use the global setting then in your particular config you'd need to have signaling forward on both your 7788000 and 7780000 dial-peers.  As it is now, the SIP INFO message tunneling the request is being sent to the dialer session but the response can't get back to the CVP application with the call outcome so the script never resumes and nothing gets played.   You could of course use a single combined incoming and outgoing dial-peer with both incoming called number and destination pattern configured on it.

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: Paul Tindall on 24-08-2011 05:35:58 AM
Subsequent VoiceXML transfers should work absolutely fine; I've never had a problem with them.

Q.  How is cvp_dialer invoked?

1.  The custom Makecall element generates a VoiceXML document which uses an <object> element to temporarily handoff the call leg to the TCL script cvp_obcallreq.tcl, passing an argument string containing the dialing parameters derived from the Makecall element settings.

2. cvp_obcallreq.tcl sends a SIP INFO message to the cvp_outbound.tcl session that's active at the calling end of the polling call.

3. cvp_outbound.tcl hands-off the originating end of the polling call to a new cvp_dialer.tcl session together with the dialing parameters.

4. cvp_outbound.tcl immediately re-polls to initiate the next outbound call if there is one ready to go.

5. cvp_dialer.tcl is running in parallel and makes the outbound call and returns the call outcome back to cvp_obcallreq.tcl via a SIP INFO message when the attempt is established or fails due to busy, no answer, etc.

I seem to recall there's a diagram in the config document that shows the flow.   Also the mechanism is documented in a Networkers session slide deck BRKUCT-3015 Advanced Tips and Tricks for Self-Service Application Development using Cisco Unified Call Studio which seems to have become pretty much public domain if you search for it.  Also, I've attached the section on the outbound mechanism as the whole deck is a bit big.

Hope that helps to explain it a bit.

Paul

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: Paul Tindall on 24-08-2011 05:55:21 AM
Subsequent VoiceXML transfers should work absolutely fine; I've never
had a problem with them.

Q.  How is cvp_dialer invoked?

1. 
The custom Makecall element generates a VoiceXML document which uses an
<object> element to temporarily handoff the call leg to the TCL
script cvp_obcallreq.tcl, passing an argument string containing the
dialing parameters derived from the Makecall element settings.

2.
cvp_obcallreq.tcl sends a SIP INFO message to the cvp_outbound.tcl
session that's active at the calling end of the polling call.

3.
cvp_outbound.tcl hands-off the originating end of the polling call to a
new cvp_dialer.tcl session together with the dialing parameters.

4.
cvp_outbound.tcl immediately re-polls to initiate the next outbound
call if there is one ready to go.

5. cvp_dialer.tcl is running in
parallel and makes the outbound call and returns the call outcome back
to cvp_obcallreq.tcl via a SIP INFO message when the attempt is
established or fails due to busy, no answer, etc.

I seem to
recall there's a diagram in the config document that shows the flow.  
Also the mechanism is documented in a Networkers session slide deck
BRKUCT-3015 Advanced Tips and Tricks for Self-Service Application
Development using Cisco Unified Call Studio which seems to have become
pretty much public domain if you search for it.  Also, I've attached the
section on the outbound mechanism as the whole deck is a bit big.

Hope
that helps to explain it a bit.
 
Paul

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: CLAUDIO RIVAS on 28-09-2011 12:21:07 AM
Hi Paul,

After some testings we are able to place the outbound call and to ip phones on a initial phase and seems to be working fine, but on a second phase we are trying to reach customers with this application by a E1 ISDN trunk, but calls are not getting connected for some reasons, on cvp logs i'm getting an invalid number message from the Makecall step and on the gateway i see disconnections with cause 28 codes (invalid number).
What can be causing the issue and how can i handle it?

Regards,
Claudio.

Subject: RE: outbound_dialing_in_CVP Standalone problem
Replied by: Paul Tindall on 28-09-2011 04:37:47 AM
Claudio,
Your network doesn't like the number you're sending so I'd start with a "deb isdn q931" trace.  Have you tried the same gateway config and POTS dial-peer to make normal outgoing calls to the PSTN from an IP phone?   If those work, then I'd certainly try comparing the ISDN debug for both of them.
CreatePlease to create content
Content for Community-Ad
FusionCharts will render here