Forwarding the call via R2/ISDN channelForwarding the call via R2/ISDN channelhttp://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=62669472013-05-20T01:12:47Z2013-05-20T01:12:47ZRE: Forwarding the call via R2/ISDN channelRaghavendra Gutty Veeranagappahttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=64227072012-09-05T07:24:01Z2012-09-05T07:24:01Zaddressed in below thread.
http://developer.cisco.com/web/vgapi/forums/-/message_boards/view_message/6266943Raghavendra Gutty Veeranagappa2012-09-05T07:24:01ZForwarding the call via R2/ISDN channelJean Lofranohttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=62669462012-09-05T07:15:33Z2012-08-10T14:28:57ZHi team!!!
I have a solution working properly. But I have a problem of the sizing.
The script has the flow:
Incoming call > third part PBX >> ISDN/R2 integration >> Router with TCL script.
The user can to hear the welcome prompt, but when the user choose the option to forward the call for HelpDesk the integration will busy 2 channels.
It can be a problem for me, because the environemnt has in around 1500 people.
Is there any feature for the router leave the call after a transfer?
thanks.
proc CallHelpDesk { } {
global CallerID
puts "Fowarding to Help Desk"
set callinfo(originationNum) $CallerID
set callinfo(alertTime) 10
set destination 79889
puts "FAZENDO CHAMADA"
leg setup $destination callinfo leg_outgoing
#fsm setstate CALLEDHELPDESK
}
proc CheckCallSetup { } {
puts "IT7 ------------ chamada realizada"
set statuscall [infotag get evt_status]
switch $statuscall {
"ls_000" {
puts "CHAMADA ATIVA"
set incoming [infotag get leg_incoming]
puts "Parte 2"
set outgoing [infotag get leg_outgoing]
connection create $incoming $outgoing
}
defaul {
puts "CHAMADA FALHOU"
}
}
puts "CHECK CALL SETUP ACABOU"
}Jean Lofrano2012-08-10T14:28:57Z