Post new topic Reply to topic  [ 2 posts ] 

Board index : TeleFlow Forums : TeleFlow Server & Monitor

Author Message
 Post subject:
PostPosted: Thu Apr 14, 2005 4:14 pm 
Offline

Joined: Tue Mar 18, 2003 5:52 pm
Posts: 54
Location: Canada
A common error at the "Wait for Call step" appears as if the TFServer has not been licensed. <br> <br>Apr 14 15:01:57.25: [55] Wait for Call <br>Apr 14 15:01:57.25: WARNING: TIMEOUT '0' evaluates to 0 and is interpreted as no timeout <br>Apr 14 15:01:58.75: Wait for 2 rings and then pickup <br>Apr 14 15:01:58.75: ERROR: Port 1 specified exceeds maximum ports (0) <br>Apr 14 15:01:58.75: FATAL <br>Apr 14 15:01:58.75: Attempting to jump to Fatal Error Global Event label: 'BIGEND' <br> <br>In fact, what has occured is that TFServer was not able to locate any active hardware ports. Chances are, the Dialogic / NMS / AiLogix or other hardware service was not correctly started.


Back to top
 Profile WWW 
 
 Post subject:
PostPosted: Thu Apr 14, 2005 4:15 pm 
Offline

Joined: Tue Mar 18, 2003 5:52 pm
Posts: 54
Location: Canada
An following is an example showing TFServer not being able to locate any active hardware ports. <br> <br>Apr 14 15:01:57.25: [55] Wait for Call <br>Apr 14 15:01:57.25: WARNING: TIMEOUT '0' evaluates to 0 and is interpreted as no timeout <br>Apr 14 15:01:58.75: Wait for 2 rings and then pickup <br>Apr 14 15:01:58.75: ERROR: Port 1 specified exceeds maximum ports (0) <br>Apr 14 15:01:58.75: FATAL <br>Apr 14 15:01:58.75: Attempting to jump to Fatal Error Global Event label: 'BIGEND'


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

Board index : TeleFlow Forums : TeleFlow Server & Monitor


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.