Numeric paging and alpha paging are using different queue's internaly.  This means that IF both should be able to work together that you should use 2 modems (and thus 2 lines too).
Are we planning on changing this?  No.  Why?  Numeric paging is for us an feature to discard since it's not reliable due to the fact that it's not protocol based.  The only reason why we leave it in the product is because it seems that alpha paging is rather slow in catching on in the US.
 
 
 

Dirk.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Fuller
Sent: Monday, February 16, 2004 9:15 PM
To: [EMAIL PROTECTED]
Subject: [SA-list] Using Numeric and Alpha Pagers together

We have one team member that uses a numeric pager and one that uses an alphanumeric pager.  When we set an alert to a numeric, the alert gets sent to the numeric pager successfully.  When we set an alert to the alpha pager, it gets sent sucessfully.  BUT when we set both alerts on the same entry, only the alpha pager gets the alert.  Looking at the log, it appears that the numeric pager is trying to get it's alert while the modem is talking to the alpha pager.  Below is a few lines from the log:
 
Monday, February 16, 2004 1:40:22 PM TO convert : (PID= 1) to 5620,,,,1380
Monday, February 16, 2004 1:40:22 PM TAPI request queued
Monday, February 16, 2004 1:40:22 PM TO convert : (PID= 2) to 9864137
Monday, February 16, 2004 1:40:22 PM PAGING : Comm  1
Monday, February 16, 2004 1:40:22 PM PAGING : RECIP 9864137
Monday, February 16, 2004 1:40:22 PM PAGING : REQ F
Monday, February 16, 2004 1:40:22 PM PAGING : TEXT Host Query is DOWN
Monday, February 16, 2004 1:40:22 PM PAGING : SMSC 9,9864399,,,,
Monday, February 16, 2004 1:40:22 PM PAGING : PROTO  1
Monday, February 16, 2004 1:40:22 PM TAP DEBUG: Starting sending thread. ( 26400)
Monday, February 16, 2004 1:40:22 PM TAP DEBUG: Sending thread starting up. ( 26400)
Monday, February 16, 2004 1:40:22 PM TAP DEBUG: Logon procedure started. ( 26101)
Monday, February 16, 2004 1:40:22 PM DPLB LIS Computer
Monday, February 16, 2004 1:40:22 PM Starting new TAPI page
Monday, February 16, 2004 1:40:22 PM NumDevices: 6 - lineInitalize
Monday, February 16, 2004 1:40:22 PM Dev #0 supports ver 10004 - LineNegAPI
Monday, February 16, 2004 1:40:22 PM Dev #1 supports ver 10003 - LineNegAPI
Monday, February 16, 2004 1:40:22 PM Dev #2 supports ver 10004 - LineNegAPI
Monday, February 16, 2004 1:40:22 PM Dev #3 supports ver 10004 - LineNegAPI
Monday, February 16, 2004 1:40:22 PM Dev #4 supports ver 10004 - LineNegAPI
Monday, February 16, 2004 1:40:22 PM Dev #5 supports ver 10004 - LineNegAPI
Monday, February 16, 2004 1:40:22 PM 10 - lineOpen
Monday, February 16, 2004 1:40:22 PM TAPI - Send to modem : 5620,,,,1380,,,,76*0#
Monday, February 16, 2004 1:40:22 PM Call placed! (5620,,,,1380,,,,76*0#) - lineMakeCall (1:40:22 PM)
Monday, February 16, 2004 1:40:22 PM LINE_REPLY [12] ReqID: 65877
Monday, February 16, 2004 1:40:45 PM LINEERR_INVALCALLHANDLE [80000018] - lineDrop (1:40:45 PM)
Monday, February 16, 2004 1:40:45 PM Had some problems during the page
 
We have tried putting the persons in teams and setting the alerts for the default team and we have tried different orders of persons when setting the alerts.  Everything we seem to do produces the same outcome.  Are we missing something?
 
Thanks
Randy

Reply via email to