Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet
- DevNet Collaboration
- Collaboration Knowledge Base
- Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
1444
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-25-2014 10:37 AM
This document was generated from CDN thread
Created by: Gerard O'Rourke on 18-03-2013 02:00:43 PM
I would like to be able to catch a hang-up event following a call transfer.
Because I need to catch this AFTER a call transfer, I don't believe I can use CVP Studio application to catch this event?
i.e. as it does not support using the call transfer element when used in CVP Comprehensive mode (CVP CallServer + ICM).
So Ideally CVP CallServer would catch this event, and I could run a ICM script which could trigger a CVP Studio Application which could run some custom Java code.
However I don't believe that this is possible.
Maybe I could use a standalone CVP studio application to do this?
i.e. where I coudl use a CVP Studio Transfer Element and also catch the Hang-up event?
But I need to trigger this call from an ICM Script (as I need to capture some variables from the Agent Desktop), so I could route to a label, which would route to a CVP Gateway which would trigger a standalone app?
Any thoughts / ideas?
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Asher Schweigart on 20-03-2013 02:17:06 PM
Once ICM makes the transfer, CVP has no control over the call, so you would not be able to catch the hangup event, unless the transfer was to another ICM number.
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Sidney Orret on 22-03-2013 07:26:56 PM
On a different but similar thread I commented about this. Once the call is transferred the solution is not on ICM or VXML app. To catch the hangup event either on ICM or a VXML application you would need to do a conference not a transfer so ICM or VXML app stays on the call until one of the other parties drops. The main problem is that conference functionality is not available on either of them. The main issue is that once the transfer is completed ICM or the VXML app don't have control or visibility of the call anymore.
The only two devices that are still engaged on a transferred call are the ingress GW and the CVP Call Server. I think the best route to explore is a TCL script ion the GW that (just an idea) triggers an http request and pass some parameters to a VXML application that then takes care of the post call processing.
[quote=Gerard O'Rourke]I would like to be able to catch a hang-up event following a call transfer.
Because I need to catch this AFTER a call transfer, I don't believe I can use CVP Studio application to catch this event?
i.e. as it does not support using the call transfer element when used in CVP Comprehensive mode (CVP CallServer + ICM).
So Ideally CVP CallServer would catch this event, and I could run a ICM script which could trigger a CVP Studio Application which could run some custom Java code.
However I don't believe that this is possible.
Maybe I could use a standalone CVP studio application to do this?
i.e. where I coudl use a CVP Studio Transfer Element and also catch the Hang-up event?
But I need to trigger this call from an ICM Script (as I need to capture some variables from the Agent Desktop), so I could route to a label, which would route to a CVP Gateway which would trigger a standalone app?
Any thoughts / ideas?
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 23-03-2013 01:39:27 PM
If you want to use CVP Standalone you could transfer your caller to standalone via ICM / CVP Call Server and send the necessary context data via SIP headers. I did recently post some info on accessing SIP headers from a Call Studio applcation. Using a custom transfer element it is also possible to trap caller hangup while the transfer is in progress and pass control back to the application for some final processing. I did also post a sample on that topic some time ago when someone else had the same request. Might be hard to find on the forum and may need to be posted again. Howvere, just to see if it works for you, if you have 9.0 in the lab then try using the VideoConnect element to do your transfer as that includes the caller hangup detection.
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 11-04-2013 11:25:50 AM
Paul,
Thanks for your response. I missed your response when you sent it. Just seeing it now.
It's very interesting.
Are you saying its OK to send to a call into CVP Standalone from a CVP CallServer /ICM (i.e. a 'CVP Comphensive Call into CVP Standalone).
I thought this would be good way to catch the hangup event, but I did not know how to send variables into the standalone app, which would be needed.
Where's the best place me me to look on how to you set custom SIP Headers information from a CVP CallServer/ICM call into the standalone app?
Could not find your recent discussion on retrieving SIP headerd from within a CVP studio app. If you could post the URL it would be great. I will keep looking!
Thanks,
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 12-04-2013 05:31:25 AM
Just sending the call from the CVP Call Server to a Standalone CVP is technically no different from sending the call to any other egress gateway, however, you might want to consider using a REFER so the CVP Call Server drops out and simplifies the signalling a bit. What is not supported is performing subsequent transfers via a Studio app while being used for VRU treatment in the standard comprehensive model.
Slides on SIP header getting/setting re-posted.
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 14-04-2013 10:24:00 AM
Many thanks Paul. This looks great.
Just have to get some time now and try it out!
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 15-04-2013 06:31:21 AM
Paul,
Is it possible to get a copy of the TCLTransfer custom element and relevant TCL scripts which are documented in the "Getting and Setting SIP Headers" PDF?
i.e. uploaded up onto CDN or as a attachment to this discussion?
There were links to the TCLTransfer attachements in another discussion, but the attachement is no longer available.
If the GetSIPHeader & TCLTransferWhisper are also available, these would be really useful too. Its a great feature to have.
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 15-04-2013 05:35:26 PM
Gerry,
There's one transfer variant I posted on a different thread a few days ago http://developer.cisco.com/web/cvp/community/-/message_boards/message/14152374#_19_message_14194913
I've attached a slightly different transfer here as well as the get SIP header element. I do aim to merge the transfer branches and post more on CDN Downloads as it so hard to find posted items in threads -- I just need a slot to complete a bit of documentation.
Remember the usual caveat for things I post here, they're sold-as-seen and won't get support via Cisco TAC. If you can live with that limitation, then please enjoy and make use of them.
Paul
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 17-04-2013 03:48:19 AM
Paul,
I fully understand the rataional around the support caveat.
As always much appreciated. Thanks again.
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 26-04-2013 11:51:06 AM
Paul,
The GetSipHeader works fine for me. Thanks a million.
The TCLTransfer1.0.3 does sucesfully transfer, but its not setting the SIP header, Any ideas?
Does it need a specific IOS (using c2801-advipservicesk9-mz.151-4.M5.bin)
Below is an extract from the debug from the gateway using the command "debug voip application script"
This suggest the TCL script has the header value.
Also attached is the SIP INVITE sent out from the Gateway, which I expected to see a header of "CallSeqPQ: blah", but no custom header in it.
TCL Extract Debug:
Apr 26 16:39:37.193: //133//TCL :/tcl_PutsObjCmd: CVP_TCLXFER, assumed control of call with argument: <dest=11110 rna=20 pause=0 tonedur=100 tonegap=100 disc=false reco=false siphdr=(CallSeqPQ:blah)>
SIP INVITE Debug:
INVITE sip:11110@192.168.1.161:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.130:5060;branch=z9hG4bK3897
From: <sip:192.168.1.130>;tag=C9650-E98
To: <sip:11110@192.168.1.161>
Date: Fri, 26 Apr 2013 16:39:37 GMT
Call-ID: B7C6DF31-ADC611E2-80CCA403-5CD49AA4@192.168.1.130
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1194768204-0268435774-2023186374-1062731359
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1366994377
Contact: <sip:192.168.1.130:5060>
Expires: 60
Allow-Events: telephone-event
Max-Forwards: 68
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 248
v=0
o=CiscoSystemsSIP-GW-UserAgent 5152 3218 IN IP4 192.168.1.130
s=SIP Call
c=IN IP4 192.168.1.30
t=0 0
m=audio 10646 RTP/AVP 0 101
c=IN IP4 192.168.1.30
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 27-04-2013 06:41:09 AM
Gerry,
There's nothing special that needs to be turned on to enable the SIP headers and your IOS version should be fine.
I can't tell from the trace snippet but is your incoming call leg TDM or SIP? I'd suspect it might be the latter. If so, that particular custom transfer version won't insert headers. Unfortunately, the transfer call leg setup has to be done a bit differently in the TCL to make that happen.
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 29-04-2013 02:33:03 AM
Paul,
You are spot on. The inbound call leg was SIP.
No chance you that you have created a custom TCL script which does the same for a SIP inbonud leg?
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 29-04-2013 04:10:12 AM
OK. Thanks for the update & your help.
if / when one available. Let us know!
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 29-04-2013 04:06:32 AM
Unfortunately, don't have one ready-built at the moment although it would be useful to have it working for SIP-SIP.
Created by: Gerard O'Rourke on 18-03-2013 02:00:43 PM
I would like to be able to catch a hang-up event following a call transfer.
Because I need to catch this AFTER a call transfer, I don't believe I can use CVP Studio application to catch this event?
i.e. as it does not support using the call transfer element when used in CVP Comprehensive mode (CVP CallServer + ICM).
So Ideally CVP CallServer would catch this event, and I could run a ICM script which could trigger a CVP Studio Application which could run some custom Java code.
However I don't believe that this is possible.
Maybe I could use a standalone CVP studio application to do this?
i.e. where I coudl use a CVP Studio Transfer Element and also catch the Hang-up event?
But I need to trigger this call from an ICM Script (as I need to capture some variables from the Agent Desktop), so I could route to a label, which would route to a CVP Gateway which would trigger a standalone app?
Any thoughts / ideas?
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Asher Schweigart on 20-03-2013 02:17:06 PM
Once ICM makes the transfer, CVP has no control over the call, so you would not be able to catch the hangup event, unless the transfer was to another ICM number.
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Sidney Orret on 22-03-2013 07:26:56 PM
On a different but similar thread I commented about this. Once the call is transferred the solution is not on ICM or VXML app. To catch the hangup event either on ICM or a VXML application you would need to do a conference not a transfer so ICM or VXML app stays on the call until one of the other parties drops. The main problem is that conference functionality is not available on either of them. The main issue is that once the transfer is completed ICM or the VXML app don't have control or visibility of the call anymore.
The only two devices that are still engaged on a transferred call are the ingress GW and the CVP Call Server. I think the best route to explore is a TCL script ion the GW that (just an idea) triggers an http request and pass some parameters to a VXML application that then takes care of the post call processing.
[quote=Gerard O'Rourke]I would like to be able to catch a hang-up event following a call transfer.
Because I need to catch this AFTER a call transfer, I don't believe I can use CVP Studio application to catch this event?
i.e. as it does not support using the call transfer element when used in CVP Comprehensive mode (CVP CallServer + ICM).
So Ideally CVP CallServer would catch this event, and I could run a ICM script which could trigger a CVP Studio Application which could run some custom Java code.
However I don't believe that this is possible.
Maybe I could use a standalone CVP studio application to do this?
i.e. where I coudl use a CVP Studio Transfer Element and also catch the Hang-up event?
But I need to trigger this call from an ICM Script (as I need to capture some variables from the Agent Desktop), so I could route to a label, which would route to a CVP Gateway which would trigger a standalone app?
Any thoughts / ideas?
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 23-03-2013 01:39:27 PM
If you want to use CVP Standalone you could transfer your caller to standalone via ICM / CVP Call Server and send the necessary context data via SIP headers. I did recently post some info on accessing SIP headers from a Call Studio applcation. Using a custom transfer element it is also possible to trap caller hangup while the transfer is in progress and pass control back to the application for some final processing. I did also post a sample on that topic some time ago when someone else had the same request. Might be hard to find on the forum and may need to be posted again. Howvere, just to see if it works for you, if you have 9.0 in the lab then try using the VideoConnect element to do your transfer as that includes the caller hangup detection.
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 11-04-2013 11:25:50 AM
Paul,
Thanks for your response. I missed your response when you sent it. Just seeing it now.
It's very interesting.
Are you saying its OK to send to a call into CVP Standalone from a CVP CallServer /ICM (i.e. a 'CVP Comphensive Call into CVP Standalone).
I thought this would be good way to catch the hangup event, but I did not know how to send variables into the standalone app, which would be needed.
Where's the best place me me to look on how to you set custom SIP Headers information from a CVP CallServer/ICM call into the standalone app?
Could not find your recent discussion on retrieving SIP headerd from within a CVP studio app. If you could post the URL it would be great. I will keep looking!
Thanks,
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 12-04-2013 05:31:25 AM
Just sending the call from the CVP Call Server to a Standalone CVP is technically no different from sending the call to any other egress gateway, however, you might want to consider using a REFER so the CVP Call Server drops out and simplifies the signalling a bit. What is not supported is performing subsequent transfers via a Studio app while being used for VRU treatment in the standard comprehensive model.
Slides on SIP header getting/setting re-posted.
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 14-04-2013 10:24:00 AM
Many thanks Paul. This looks great.
Just have to get some time now and try it out!
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 15-04-2013 06:31:21 AM
Paul,
Is it possible to get a copy of the TCLTransfer custom element and relevant TCL scripts which are documented in the "Getting and Setting SIP Headers" PDF?
i.e. uploaded up onto CDN or as a attachment to this discussion?
There were links to the TCLTransfer attachements in another discussion, but the attachement is no longer available.
If the GetSIPHeader & TCLTransferWhisper are also available, these would be really useful too. Its a great feature to have.
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 15-04-2013 05:35:26 PM
Gerry,
There's one transfer variant I posted on a different thread a few days ago http://developer.cisco.com/web/cvp/community/-/message_boards/message/14152374#_19_message_14194913
I've attached a slightly different transfer here as well as the get SIP header element. I do aim to merge the transfer branches and post more on CDN Downloads as it so hard to find posted items in threads -- I just need a slot to complete a bit of documentation.
Remember the usual caveat for things I post here, they're sold-as-seen and won't get support via Cisco TAC. If you can live with that limitation, then please enjoy and make use of them.
Paul
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 17-04-2013 03:48:19 AM
Paul,
I fully understand the rataional around the support caveat.
As always much appreciated. Thanks again.
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 26-04-2013 11:51:06 AM
Paul,
The GetSipHeader works fine for me. Thanks a million.
The TCLTransfer1.0.3 does sucesfully transfer, but its not setting the SIP header, Any ideas?
Does it need a specific IOS (using c2801-advipservicesk9-mz.151-4.M5.bin)
Below is an extract from the debug from the gateway using the command "debug voip application script"
This suggest the TCL script has the header value.
Also attached is the SIP INVITE sent out from the Gateway, which I expected to see a header of "CallSeqPQ: blah", but no custom header in it.
TCL Extract Debug:
Apr 26 16:39:37.193: //133//TCL :/tcl_PutsObjCmd: CVP_TCLXFER, assumed control of call with argument: <dest=11110 rna=20 pause=0 tonedur=100 tonegap=100 disc=false reco=false siphdr=(CallSeqPQ:blah)>
SIP INVITE Debug:
INVITE sip:11110@192.168.1.161:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.130:5060;branch=z9hG4bK3897
From: <sip:192.168.1.130>;tag=C9650-E98
To: <sip:11110@192.168.1.161>
Date: Fri, 26 Apr 2013 16:39:37 GMT
Call-ID: B7C6DF31-ADC611E2-80CCA403-5CD49AA4@192.168.1.130
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1194768204-0268435774-2023186374-1062731359
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1366994377
Contact: <sip:192.168.1.130:5060>
Expires: 60
Allow-Events: telephone-event
Max-Forwards: 68
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 248
v=0
o=CiscoSystemsSIP-GW-UserAgent 5152 3218 IN IP4 192.168.1.130
s=SIP Call
c=IN IP4 192.168.1.30
t=0 0
m=audio 10646 RTP/AVP 0 101
c=IN IP4 192.168.1.30
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 27-04-2013 06:41:09 AM
Gerry,
There's nothing special that needs to be turned on to enable the SIP headers and your IOS version should be fine.
I can't tell from the trace snippet but is your incoming call leg TDM or SIP? I'd suspect it might be the latter. If so, that particular custom transfer version won't insert headers. Unfortunately, the transfer call leg setup has to be done a bit differently in the TCL to make that happen.
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 29-04-2013 02:33:03 AM
Paul,
You are spot on. The inbound call leg was SIP.
No chance you that you have created a custom TCL script which does the same for a SIP inbonud leg?
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Gerard O'Rourke on 29-04-2013 04:10:12 AM
OK. Thanks for the update & your help.
if / when one available. Let us know!
Gerry
Subject: RE: Catch a Hang-up Event - CVP/ICM script (not within a CVP Studio App)
Replied by: Paul Tindall on 29-04-2013 04:06:32 AM
Unfortunately, don't have one ready-built at the moment although it would be useful to have it working for SIP-SIP.
Labels:
Getting Started
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:
Customers Also Viewed These Support Documents