I recently built out an ICM / CVP 8.0 environment. I started my first ICM script to send to an agent and that worked great with CTIOS.
I proceed to use a PM microapp to play a .wav file (8bit u-law mono) and it will not work. On the phone it just plays silence and hangs up the call after 11 seconds. I have done "debug http client error" on my VXML gateway and nothing showed up (odd). I then did "debug http client all" and sifted through that log to fine some kind of relevant information, although I do not know how to interpret it.
When I put that URL into my web browser it plays the .wav file, so I know the URL is valid. If anyone needs any addition information about this issue please reply and I will get it for you.
Subject: Re: New Message from Deven Patterson in Customer Voice Portal (CVP) - CVP - Replied by: Janine Graves on 06-02-2013 08:38:30 PM sounds like it's encoded in the wrong format to me.
Subject: RE: Re: New Message from Deven Patterson in Customer Voice Portal (CVP) - C Replied by: Deven Patterson on 07-02-2013 08:51:42 AM
Janine Graves:
sounds like it's encoded in the wrong format to me.
Hmm I used my same .wav files from ICM 7.5(2) and they worked, has the encoding type changed since then?
Subject: Re: New Message from Deven Patterson in Customer Voice Portal (CVP) - CVP - Replied by: Janine Graves on 07-02-2013 01:40:30 PM What do you have configured on the gateway for the codec?
Subject: RE: Re: New Message from Deven Patterson in Customer Voice Portal (CVP) - C Replied by: Deven Patterson on 07-02-2013 01:50:23 PM
Janine Graves:
What do you have configured on the gateway for the codec?
Subject: RE: Re: New Message from Deven Patterson in Customer Voice Portal (CVP) - C Replied by: Janine Graves on 07-02-2013 02:22:33 PM This is beyond my expertise. Maybe someone else can help. But, I did notice that you only have 2 dial peers configured that specify your voice-class codec 8. Is one of these dial-peers the one giving you trouble? dial-peer voice 4002 voip destination-pattern 8585550151 voice-class codec 8 session protocol sipv2 session target ipv4:10..x.x.x dtmf-relay rtp-nte h245-signal h245-alphanumeric no vad ! dial-peer voice 4003 voip service vru-leg voice-class codec 8 session protocol sipv2 incoming called-number 1234567891T dtmf-relay rtp-nte h245-signal h245-alphanumeric no vad !
Subject: RE: Re: New Message from Deven Patterson in Customer Voice Portal (CVP) - C Replied by: Deven Patterson on 07-02-2013 02:36:17 PM
Janine Graves:
This is beyond my expertise. Maybe someone else can help. But, I did notice that you only have 2 dial peers configured that specify your voice-class codec 8. Is one of these dial-peers the one giving you trouble?
dial-peer voice 4002 voip destination-pattern 8585550151 voice-class codec 8 session protocol sipv2 session target ipv4:10..x.x.x dtmf-relay rtp-nte h245-signal h245-alphanumeric no vad ! dial-peer voice 4003 voip service vru-leg voice-class codec 8 session protocol sipv2 incoming called-number 1234567891T dtmf-relay rtp-nte h245-signal h245-alphanumeric no vad !
Nah the dialpeers are fine. They worked to get a call to an agent at least. Also, pretty sure other then the transfer label + Corelation ID dialpeer you don't even need any others for a PM microapp.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
