vxml "blind transfer" and fxo

Version 1
    This document was generated from CDN thread

    Created by: rost beef on 01-12-2009 12:26:43 AM
    Hello, I was interested in vxml   8)
    I have appeared, one intractable problem.
    Can means vxml, get busy port fxo make flash aka hookflash.
    In vxml is called blind transfer.
    schematic example:
     co-PBX-ext101 -> fxo0/1--ios_vxml
            |
         ext102 -> operator
    I want to understand how you can get from ios_vxml send to the port 'fxo' flash command with the number '101' on the pbx, to call from the 'co' switched to the number '102'.
     
     
     
    Rostisav Prilepov
    Russia 198320 St.-Petersburg
    dest="tel:+79213299737"

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Anusha Kannappan on 01-12-2009 10:25:08 AM
    Hi Rost,
     
    You can make use of the <transfer> tag for achieving the blind transfer by setting the bridge as false or setting the type as blind.
     
    Thanks,
    Anusha.

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: rost beef on 01-12-2009 11:11:52 AM
    25 <form id="call">
    26     <transfer name="IVR_call" type="blind" dest="102" bridge="false"></transfer>
    27 </form>
    debug <191>9751: at line 26: : <transfer type> Unknown attlist 
     
    Click in lines, and then a breakaway is audible!
     

    11469: name=IVR_call 
    11470: URI(abs):tel:102 
    11471: scheme=tel 
    11472: path=102 bridge=0 connecttimeout=0 maxtime=0 desttype=-1 destplan=-1 anitype=-1 aniplan=-1 anipi=-1, anisi=-1 rdntype=-1 rdnplan=-1 rdnpi=-1, rdnsi=-1, redirectreason=-1 
    11473: Nov 26 15:19:43.787: //-1//VXML:/vxml_play_prompts: Enter 
    11474: Nov 26 15:19:43.787: //-1//VXML:/vxml_play_prompts: Exit 
    11475: Nov 26 15:19:43.791: //467/F03E57D48304/VXML:/vxml_transfer_proc: 
    11477: GTD not present in <transfer> 
    11478: Nov 26 15:19:43.791: //-1//VXML:/vxml_generic_digit_collect: Enter 
    11479: Nov 26 15:19:43.791: //467/F03E57D48304/VXML:/vxml_vapp_placecall: 
    11480: dest tel:102 timeout 0 maxlength 0, longpound 1, newguid 0 hoString NULL type=2 
    11481: Nov 26 15:19:43.791: //467/F03E57D48304/VXML:/vxml_vapp_gain_control_default: 
    11483: Nov 26 15:19:43.791: //467//AFW_:/vapp_gain_control_default: 
    11484: Nov 26 15:19:43.795: //467//AFW_:/vapp_placecall: 
    11485: Nov 26 15:19:43.795: //467//AFW_:/vapp_sendevent: Name: transfer, SessionEvent: TRUE 
    11486: Nov 26 15:19:43.795: //467//AFW_:/vapp_sendevent: event-name: vxml.session.transfer 
    11487: Nov 26 15:19:43.795: //-1//VXML:/vxml_vapp_placecall: Exit 
    11488: Nov 26 15:19:43.795: //-1//VXML:/vxml_transfer_proc: Exit 
    11489: Nov 26 15:19:43.795: //-1//VXML:/vxml_elem_proc: 
    11490: (80000000) Status not OK, exit@9899 
    11491: Nov 26 15:19:43.795: //467/F03E57D48304/VXML:/vxml_formitem_select: 
    11492: loop cnt=0, 
    11493: Nov 26 15:19:43.795: //-1//VXML:/vxml_formitem_select: 
    11494: (80000000) Status not OK, exit@5405 
    11495: Nov 26 15:19:43.799: //-1//VXML:/vxml_form_proc: 
    11525: Nov 26 15:19:43.815: //467/F03E57D48304/VXML:/vxml_cancel_hotword:

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: rost beef on 01-12-2009 12:38:17 PM
    I am use c1700-advipservicesk9-mz.124-15.T11
     

    Cisco IOS Release 12.4(15)T adds support for Media Resource
    Control Protocol version 2 (MRCP v2) servers and VoiceXML 2.1

     
    in link http://www.vxml.org/frame.jsp?page=transfer.htm
    Has seen
     blind transfers or SIP REFER, this service requires dedicated telephone resources  8(

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Vijay Prasad Neelamegam on 01-12-2009 11:21:54 AM
    Hi Rost,
     
    The type attribute is a new inclusion per the VoiceXML 2.1 specification,
    and allows the developer a means of specifying the type of call transfer to be
    performed.
     
    What version you are using.Kindly go through the following link.
     
    http://www.vxml.org/frame.jsp?page=transfer.htm
     
    Hope this helps
     
    Regards
    Vijay

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Anusha Kannappan on 02-12-2009 06:13:14 AM
    Hi Rost,
     
    Exactly one of the "bridge" or "type" attributes may be specified; otherwise an error.badfetch event is throuwn.
     
    For more details you can check the following link 
    http://www.w3.org/TR/voicexml21/
     
    Since all of the functionality of the bridge attribute has been incorporated into the type attribute, developers are encouraged to use the type attribute on platforms that implement it.
     
    Please try and see and let us know if you further end up in issue. 
     
    Thanks,
    Anusha.

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: rost beef on 28-12-2009 04:17:41 PM
    <form id="call" scope="dialog">
      <transfer name="IVR_call" type="blind" dest="tel://102"/>
    </form>

     
    Does not work

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Anusha Kannappan on 29-12-2009 10:29:55 AM
    Hi Roost,
     
    Please try after modifying the dest tel uri as dest="tel:+102" as shown below 
     
    <form id="call" scope="dialog">
    <transfer name="IVR_call" type="blind" dest="tel:+102"/>
    </form>
     
    Thanks,
    Anusha

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: rost beef on 30-12-2009 09:49:54 AM
    Not work too
    I have attached a syslog file

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Anusha Kannappan on 30-12-2009 12:59:43 PM
    Hi Rost,
     
    Can you please attach the script to debug further.
     
    Thanks,
    Anusha.

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: rost beef on 30-12-2009 03:17:01 PM
    attached the script

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Anusha Kannappan on 31-12-2009 01:08:50 PM
    Hi Rost,
     
    You can try blind transfer by just setting bridge=false. Also you need to check for the ephone setting of the interpreter. Have to set "transfer-mode blind" for the ephone.
     
    Thanks,
    Anusha

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: rost beef on 22-01-2010 01:50:08 PM
    this transfer for fxo port only, no use ephone or ip phone

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Vijay Prasad Neelamegam on 25-01-2010 06:38:51 AM
    Hi Rost,
     
    For Blind Transfer there is an example sample script in the following link
    http://developer.cisco.com/c/document_library/get_file?folderId=1399664&name=DLFE-22006.zip
    and the file name is acme6.vxml.
     
    I went through your script,and i see transfer tag seems to be correct.But the extension of the file is .xml,can you change the extension to .vxml  and give a try.If that doesn't work please try the above sample scirpt first and update.
     
    Thanks
    Vijay

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: rost beef on 12-02-2010 04:10:57 AM
    acme6.vxml does not contain Transfer example.
    File extension does not affect his work!

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Vijay Prasad Neelamegam on 12-02-2010 05:42:48 AM
    Hi Rost,
     
    According to your trace,it seems that Transfer tag get executed and trying to find dest 102,
    Dec 30 12:41:14 1830: Dec 30 09:41:14.300: //18053/475FBE2782EE/VXML:/vxml_item_attrs_proc: 
    Dec 30 12:41:14 1831:    name=IVR_call
    Dec 30 12:41:14 1832:    URI(abs):tel:+102
    Dec 30 12:41:14 1833:    scheme=tel
    Dec 30 12:41:14 1834:    path=+102 bridge=0 connecttimeout=0 maxtime=0 desttype=-1 destplan=-1 anitype=-1 aniplan=-1 anipi=-1, anisi=-1
    Dec 30 12:41:14 1835:  rdntype=-1 rdnplan=-1 rdnpi=-1, rdnsi=-1, redirectreason=-1
     
    But Here the call get disconencted because of bad destination.
     
    Dec 30 12:41:14 1889: Dec 30 09:41:14.332: //18053/475FBE2782EE/VXML:/vxml_event_proc: 
    Dec 30 12:41:14 1890:       <event>: event=error.connection.baddestination status=0
    Dec 30 12:41:14 1891: Dec 30 09:41:14.332: //18053/475FBE2782EE/VXML:/vxml_expr_eval: 
    Dec 30 12:41:14 1892:    expr=(var _event='error.connection.baddestination')
    Dec 30 12:41:14 1893: Dec 30 09:41:14.336: //18053/475FBE2782EE/VXML:/vxml_expr_eval: 
    Dec 30 12:41:14 1894:    expr=(var _message=undefined)
    Dec 30 12:41:14 1895: Dec 30 09:41:14.336: //18053/475FBE2782EE/VXML:/vxml_default_event_handler: 
    Dec 30 12:41:14 1896:    use default event handler
    Dec 30 12:41:14 1897: Dec 30 09:41:14.340: //-1//VXML:/vxml_default_event_prompt: Enter
    Dec 30 12:41:14 1898: Dec 30 09:41:14.340: //18053//AFW_:/vapp_session_exit_event_name: Exit Event error.connection.baddestination
    Dec 30 12:41:14 1899: Dec 30 09:41:14.340: //18053/475FBE2782EE/VXML:/vxml_load_immediate_done:
     
    Can you check whether you are able to make call without invoking this script.
     
    Thanks
    Vijay

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Adolfo Arizpe on 22-02-2012 02:56:26 PM
    We are facing a similar issue.
    On a 2650XM running 12.4.21a we added this to the script:

    <?xml version="1.0"?>
    <vxml version="2.0">
    <form id="main">
       <block>
         <audio src="/audios/espere-un-momento-estamos-enviando-su-llamada-con-un-agente-disponible.g729"/>
       </block>

       <transfer name="T_1" bridge="true" dest="sip:102@200.23.90.50"></transfer>
    </form>
    </vxml>

    However, we are not able to connect, the incoming call leg remains up and we don't see an attempt to create an outbound call leg.
    The debug shows something like this
    Feb 22 19:52:44.089: //18730/9E97485980F9/VXML:/vxml_item_attrs_proc: 
       name=T_1
       URI(abs):sip:102@200.23.90.50
       scheme=sip
       path=102@200.23.90.50 bridge=0 connecttimeout=0 maxtime=0 desttype=-1 destplan=-1 anitype=-1 aniplan=-1 anipi=-1, anisi=-1 rdntype=-1 rdnplan=-1 rdnpi=-1, rdnsi=-1, redirectreason=-1
    Feb 22 19:52:44.094: //18730/9E97485980F9/VXML:/vxml_transfer_proc: 
       GTD not present in <transfer>
    Feb 22 19:52:44.094: //18730/9E97485980F9/VXML:/vxml_load_immediate_done: 
       sidp->status=180000000
    Feb 22 19:52:44.094: //18730//AFW_:/vapp_checksessionstate:
    Feb 22 19:52:44.094: //18730//AFW_:/vapp_checkifdone: Object: 1, Leg: 1
    Feb 22 19:52:49.951: //18730//AFW_:/vapp_driver: evtID: 137 vapp record state: 0
    Feb 22 19:52:49.951: //18730//AFW_:/vapp_play_done: evID=137 reason=13, protocol=2, status_code=0, dur=4716, rate=0
    Feb 22 19:52:49.951: //18730/9E97485980F9/VXML:/vxml_media_done: 
       status 0 async_status 180000000 duration=4716 rate=0
    Feb 22 19:52:49.951: //18730/9E97485980F9/VXML:/vxml_save_lastprompt_info: 
       
    Feb 22 19:52:49.951: //18730/9E97485980F9/VXML:/vxml_save_lastprompt_info: 
       
    Feb 22 19:52:49.951: //18730//AFW_:/vapp_notify_play_done:
    Feb 22 19:52:49.955: //18730/9E97485980F9/VXML:/vxml_vapp_vcr_control_disable: 
       
    Feb 22 19:52:49.955: //18730/9E97485980F9/VXML:/vxml_vapp_placecall: 
       dest sip:102@200.23.90.50 timeout 0 maxlength 0, longpound 1, newguid 0
    Feb 22 19:52:49.955: //18730/9E97485980F9/VXML:/vxml_vapp_gain_control_default: 
       
    Feb 22 19:52:49.955: //18730//AFW_:/vapp_gain_control_default:
    Feb 22 19:52:49.955: //18730//AFW_:/vapp_placecall: 
    Feb 22 19:52:49.955: //18730//AFW_:/vapp_sendevent:   Name: transfer, SessionEvent: TRUE
    Feb 22 19:52:49.955: //18730//AFW_:/vapp_sendevent: event-name: vxml.session.transfer
    Feb 22 19:52:49.959: //18730//AFW_:/vapp_checksessionstate:
    Feb 22 19:52:49.959: //18730//AFW_:/vapp_checkifdone: Object: 1, Leg: 1
    Feb 22 19:52:49.959: //18730//AFW_:/AFW_FSM_Drive: FSM no match for (WEBQUERY[7],ev_vxmldialog_event[171])

    I do have a dial peer for the destination number 102, what else could we be missing?

    dial-peer voice 102 voip
    destination-pattern 102
    session protocol sipv2
    session target ipv4:200.23.90.50
    dtmf-relay rtp-nte
    fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
    !
    sip-ua
    set sip-status 500 pstn-cause 34
    set sip-status 503 pstn-cause 34
    !
    !

    Thanks

    Subject: RE: vxml "blind transfer" and fxo
    Replied by: Raghavendra Gutty Veeranagappa on 23-02-2012 09:43:39 AM
    Hi Adolfo,

    vxml.session.transfer indicating that the document tried to execute the <transfer> element which is not supported in hybrid mode.

    The VoiceXML session started on a call leg does not support the <transfer> element. In a hybrid application, calls are transferred in Tcl using the leg setup Tcl IVR command. The leg setup command requests the system to place a call to the specified destination number. To transfer a call, the VoiceXML dialog completes its execution, and passes control to the Tcl application to perform a leg setup for the call.

    Thanks,
    Raghavendra