This is because the PM3 sends a call rejection message that is different
than what your telco needs to roll over to the next line. There doesn't
seem to be any standard between TelCos or sometimes even between switches
in the same TelCo. Lucent REALLY needs to add configuration parameters that
will allow the call reject message(s) to be configured per PM3 or even
better per line (for FX circuits) For example:
Our local TelCo says that they must receive cause code 44 (Network
Congestion Requested Channel Not Available) to roll over to the next line.
All other cause codes will be treated as a busy signal and answered with
the "All circuits are busy" voice message. The PM3 now sends cause code 17
(User busy) when it is out of modems which results in the all circuits are
busy message. This is NOT good. :( Anyone else having this same problem?
-Robert
Robert Boyle Server Co-location,
Garden Networks Internet Access,
50 Diller Ave Development & Consulting
Newton, NJ 07860 (973)300-9211 Ext.103
8AM-8PM Mon-Fri EST http://www.garden.net
Lucent RABU & Software.Com Post.Office VAR
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>