<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Announcements</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_category?p_l_id=&amp;mbCategoryId=4919011" />
  <subtitle />
  <id>http://developer.cisco.com/c/message_boards/find_category?p_l_id=&amp;mbCategoryId=4919011</id>
  <updated>2013-05-20T13:05:56Z</updated>
  <dc:date>2013-05-20T13:05:56Z</dc:date>
  <entry>
    <title>RE: New Tcl command option for "infotag get leg_dnis" and "infotag get leg_</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5806872" />
    <author>
      <name>Yaw-Ming Chen</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5806872</id>
    <updated>2012-06-01T20:22:48Z</updated>
    <published>2012-06-01T20:22:48Z</published>
    <summary type="html">Sorry that I didn't make it clear. The callnumner is a key word

The legID you can use default "leg_incoming or you can get it from evt_legs tag

set legIDs [infotag get evt_legs]

infotag get leg_dnis callnumber leg_incoming
infotag get leg_ani  callnumber  leg_incoming</summary>
    <dc:creator>Yaw-Ming Chen</dc:creator>
    <dc:date>2012-06-01T20:22:48Z</dc:date>
  </entry>
  <entry>
    <title>RE: New Tcl command option for "infotag get leg_dnis" and "infotag get leg_</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5805507" />
    <author>
      <name>Keith Haugen</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5805507</id>
    <updated>2012-06-01T16:29:46Z</updated>
    <published>2012-06-01T16:29:46Z</published>
    <summary type="html">I am not sure I am understanding -- so if I have the command translation-profile outgoing remove_prefix_89 in my dial peer, and the number dialed is 8912345, there is some way in my TCL IVR script that I can get the translated number (i.e., 12345)?  How do I determine what the [callnumber] and [legID] options should be?</summary>
    <dc:creator>Keith Haugen</dc:creator>
    <dc:date>2012-06-01T16:29:46Z</dc:date>
  </entry>
  <entry>
    <title>MSE VOIP Sample Application</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5092887" />
    <author>
      <name>Raghavendra Gutty Veeranagappa</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5092887</id>
    <updated>2012-02-02T12:13:51Z</updated>
    <published>2012-02-02T12:13:51Z</published>
    <summary type="html">Hi Cisco Developers, 
 
MSE VOIP Sample Application along with User Guide can be found under the below location.
[url=http://developer.cisco.com/web/vgapi/docs]http://developer.cisco.com/web/vgapi/docs[/url] 
 
The goal of this sample application is to demonstrate the Integration of IVR(Interactive Voice response) and MSE(Mobility service Engine).
MSE is a Context-Aware Mobility solution allows organizations to capture and integrate business processes with detailed contextual information about items such as location, temperature, availability of a person or whether an asset is in motion. This solution leverages the Unified Wireless Network to collect real-time contextual information about mobile assets and users. Once all the contextual information has been captured, calculated and stored by the Context-Aware software module, it can be made available to any business application that needs it through the Cisco Context-Aware Mobility API, which is based on Simple Object Access Protocol (SOAP) and XML protocol.
 
For more information about MSE you can refer [url=http://developer.cisco.com/web/contextaware/home]http://developer.cisco.com/web/contextaware/home[/url]
 
This Sample Application provides the single/multiple mobile client location details in a wireless Network through IVR(Interactive voice Response).
 
just download this web application &amp; deploy in any web server like tomcat have fun to add IVR(Interactive voice Response) functionality to your Mobility service Engine. 
 
Regards,
Raghavendra</summary>
    <dc:creator>Raghavendra Gutty Veeranagappa</dc:creator>
    <dc:date>2012-02-02T12:13:51Z</dc:date>
  </entry>
  <entry>
    <title>New Video under Video Tutorial</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5094716" />
    <author>
      <name>Anusha Kannappan</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5094716</id>
    <updated>2012-02-02T11:37:05Z</updated>
    <published>2012-02-02T11:02:52Z</published>
    <summary type="html">A new video has been added under [b]'Video Tutorial' [/b]covering the Anatomy of a TCL-IVR Script and walk-through of a sample TCL-IVR Script.Here is the link to view the video
[url=http://developer.cisco.com/web/vgapi/walk-through]http://developer.cisco.com/web/vgapi/walk-through[/url]</summary>
    <dc:creator>Anusha Kannappan</dc:creator>
    <dc:date>2012-02-02T11:02:52Z</dc:date>
  </entry>
  <entry>
    <title>New Tcl command option for "infotag get leg_dnis" and "infotag get leg_ani"</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4957064" />
    <author>
      <name>Yaw-Ming Chen</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4957064</id>
    <updated>2012-01-04T20:13:58Z</updated>
    <published>2012-01-04T20:13:58Z</published>
    <summary type="html">In IOS 15.2(2)T a new option [callnumber]   is introduced for infotag get leg_dnis and infotag get leg_ani

infotag get leg_dnis [callnumber] [legID]
infotag get leg_ani [callnumber] [legID]

This option services the following purposes:

1.	Return number portion only for DNIS or ANI in SIP trunk
Without
 this option we need to use regular expression to extract the number 
portion after we use ¿infotag get¿ to get the ANI or DNIS
For example:
set dnis [infotag get leg_dnis]
regexp {[0-9]+} $dnis dnis
With using this option we don¿t need to use regular expression anymore. The command will return number only.

2.
	In certain configuration if we use ¿voip-incoming translation-profile¿ 
then use after translation number to trigger Tcl script, the ¿infotag 
get leg_dnis¿ command will return the number before translation. 
For example:
The
 incoming number is 7771234 and we need have it translated to 8881234 
via ¿voip-incoming translation-profile¿ command. We will expect 8881234 
to hit Tcl application in dial-peer for incoming 8881234. Script will be
 triggered as expected but ¿infotag get leg_dnis¿ will return 7771234 
but not 8881234. Use new option can fix this issue.</summary>
    <dc:creator>Yaw-Ming Chen</dc:creator>
    <dc:date>2012-01-04T20:13:58Z</dc:date>
  </entry>
  <entry>
    <title>TCL-IVR &amp; VXML FAQ's !</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4926771" />
    <author>
      <name>Anusha Kannappan</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4926771</id>
    <updated>2011-12-22T08:51:34Z</updated>
    <published>2011-12-22T08:51:34Z</published>
    <summary type="html">We have come up with the Frequently asked questions for both the TCL-IVR and VXML API's and created the document for the same.
 
The TCL-IVR/VXML FAQ's document could be downloaded from our documentations-
[url=http://developer.cisco.com/web/vgapi/docs]http://developer.cisco.com/web/vgapi/docs[/url]
 

You can also view them in the below link
[url=http://developer.cisco.com/web/vgapi/wikidocs]http://developer.cisco.com/web/vgapi/wikidocs[/url]</summary>
    <dc:creator>Anusha Kannappan</dc:creator>
    <dc:date>2011-12-22T08:51:34Z</dc:date>
  </entry>
</feed>

