Post new topic Reply to topic  [ 5 posts ] 

Board index : TeleFlow Forums : TeleFlow Designer & Simulator

Author Message
 Post subject:
PostPosted: Mon Jun 30, 2003 11:29 am 
Offline

Joined: Wed Mar 19, 2003 4:26 pm
Posts: 36
Location: Canada
Yes. <br> <br>We use this often in T1 applications. The simplest form of this would include a wait for call step followed by compare steps with the specific @ANI that you are looking for. The true path for each of these compares could go to seperate tams of the same application. More effective yet, you could use the Run Application step, and run seperatly written applications, and have one Get900.tap.


Back to top
 Profile WWWICQ 
 
 Post subject:
PostPosted: Wed Oct 08, 2003 10:49 am 
Offline
Site Admin

Joined: Wed Dec 31, 1969 5:00 pm
Posts: 329
Location: Vancouver, BC
The new version of TeleFlow now has an example of how to do this. From the TeleFlow Designer, select "File" -> "New Application". Then chose the "Example" tab, select the icon marked "Service Branching", chose your hardware type and click "OK". <br> <br>This demo is an example, not a complete application, but it demonstrates everything you need to know to have your application react to incoming DNIS and ANI. <br> <br>If your version of TeleFlow does not have the "Service Branching" example, download the latest version from <br><a href="http://www.engenic.com/downloads.html" target="_new">http://www.engenic.com/downloads.html</a>


Back to top
 Profile WWW 
 
 Post subject:
PostPosted: Wed Feb 11, 2004 11:17 am 
Offline

Joined: Fri Jan 16, 2004 12:00 pm
Posts: 37
Location: Juarez
Does @ANI and @DNIS works only with T1 lines? <br>or those variables also populates with analog lines?


Back to top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 11, 2004 4:22 pm 
Offline

Joined: Wed Mar 19, 2003 4:28 pm
Posts: 510
Location: Canada
DIGITAL: ANI and DNIS are provided on T1 and E1. Depending on the telephony protocol and what your Telco can provide you, they may or may not both be populated to the correct location. <br> <br>In ISDN, the fields in the "Wait for Call" step are both populated with the appropriate ANI/DNIS values. <br> <br>In Wink/robbed-bit signalling, you will usually receive both in the DNIS field. You would then need to use string copies to get the individual phone numbers, and assign them to their respective @DNIS and @ANI variables.) <br> <br>ANALOG: Your @ANI variable in the "Wait for Call" step will populate on Analog IF it is being provided on the lines connected to your analog card. (If, for example, your lines are provided from a PBX, it may not be passing the ANI along, even if the PBX itself is receiving it.) <br> <br>DNIS isn't provided in analog. However, you can, if you know which number is which, create an association of ports to phone numbers. You could, for example, set up you TeleFlow Application List and your application so that you pass in the phone number for the port as @P1. You could then set @DNIS = @P1.


Back to top
 Profile WWW 
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

Board index : TeleFlow Forums : TeleFlow Designer & Simulator


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Style by Midnight Phoenix & N.Design Studio
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.