on 01-24-2014 01:41 AM
I am stuck in programing the Cisco voice gateway to support TBCT (ISDN Two B-Channel Transfer) using TCL scripting. I could not find a template from Cisco.com for the scripting and need a help from you guys to see whether any help be available for the template.
Hello,
I have simple situation that I want to get the call then transfer it to external number from VoiceGateway. So, when call hits my dial-peer script place call to that external number, and and that point I need both call legs get release.
Is this happening in this part of scrip:
proc act_CallSetupDone { } {
global beep
set status [infotag get evt_status]
if { $status == "ls_000"} {
puts " call has been hairpinned "
puts "CLI_3:END:FAIL "
} elseif {$status == "ls_040" } {
puts "call transfer sucessful status is $status "
puts "CLI_3:ENDASSED "
act_Cleanup
} else {
puts " transfer status is $status "
Let's say customer calls 4444 which is DID, then under Dial-Peer that I make exactly for that called number I send call to external number. Now at this point script receives Ls_040 as a status then call get closed.
Is this how TBCT work. Or I am not understanding this correctly?
There are REDIRECT_AT_ALERT and REDIRECT_AT_CONNECT, commonly used for TBCT.
REDIRECT_AT_ALERT -- if doing TBCT, PSTN switch will disconnect transfer by leg and trying to connect to transfer to leg. (there is a chance that transfer to leg won't get connected but transfer by leg disconnected already)
REDIRECT_AT_CONNECT transfer by leg is disconnected only when the transfer to leg is connect.
Apart from TCL script , you also need to configure IOS side for TBCT.
Thanks,
Raghavendra
Thank you,
For the IOS side, since we set " set callInfo(mode) redirect-at-alert " in our script, do we still need to do:
for the IOS configuration?
Since you have set CallInfo mode in TCL script, you don't need IOS config for this.
You need to configure TBCT commands and subscribe to TBCT from Service provider.
Thanks,
Raghavendra
Thank you,
In my case I have one PRI line, so incoming and outgoing call are both in the same PRI. So, do I still need " trunk group" , "Carrier-id ", or even "configuring outbound dial-peer for TBCT" .
My understanding says these are all needed if I have more than one PRI, otherwise the only command needed is:
isdn supp-service tbct under interface serial 0/0/0:23.
Am I correct, or those commands are all needed.
If you are using same PRI then no need of trunk group.To use TBCT, the following conditions must be met:
•PRI interface is subscribed to TBCT service from ISDN service provider.
•Both calls are voice calls.
•Both calls use the same PRI or both PRIs are part of the same trunk group.
•Incoming call is answered.
•Transfer-to number is placed as a separate call.
please refer http://www.cisco.com/c/en/us/td/docs/ios/voice/ivr/configuration/guide/tcl_c/ivr_tbct.html#wp1011922
Please contact cisco TAC if you face any issues with IOS TBCT config.
Thanks,
Raghavendra
Thank you,
I have a question about the template script. First, is this script correct and is it supposed to work?
Second,could you please briefly explain one scenario in that call gets transferred, and how script handed that. I really need to understand this.
In my situation, call hit the voicegateway, the it goes to CUCM and call gets answered. Caller and called person are talking until the called person decide to transfer call. How this activity is being handled by scrip.
The calling number is DID, so the first if is true, then call get connected ( or hairpinned) then it get transfer to external number. I want to know how it gets handle by script, while call is in a CALLACTIVE state, and I do not see :
set fsm(CALLACTIVE,ev_transfer_status) "act_CallSetupDone CALLACTIVE"
how script does the transfer part.
I really appreciated for help.
When called party decide to transfer call then the TCL script should get "ev_transfer_request" event.
Make sure that you use this command initially for reporting transfer event "infotag set evt_report "ev_transfer_request"
For more information please refer TCL IVR programming guide in below location.
Cisco DevNet: Voice Gateway API (VGAPI) - API Documents
Thanks,
Raghavendra
Thank you,
I used this script, then call rings to 4659 ( which is registered on CUCM) then 4659 transfer calls to external number, but I do not see ev_transfer_status coming to TCL.
I have application under pots dial-peer, for original incoming call to gateway from outside, BUT do I need to have application under the voip dial-peer that match with external number that 4659 transfer caller to, or that is not necessary?
I like to bring this discussion back in forum so please see my reply overther
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: