Perhaps the nature of this question is not IT-specific enough for Experts-Exchange, but I'm going to throw it out there anyway...
We are attempting to implement VoIP between two branch offices using Quintum Tenor VoIP gateways.
I am not a telecom guy -- just a "straight IT" support/development techie, learning telecom via "Trial by fire".
After 3 weeks of struggling, with tremendous support from my Quintum Reseller, here's what I know:
- we have a Norstar PBX
- full PRI (23+1 channels) providing PSTN service
- Quintum Tenor 2400 which sits as a gateway between PSTN and PBX and negotiates all calls
THE PROBLEM:
When callers who have blocked their numbers from appearing on caller ID (and possibly? LD/other callers whose numbers do not match their call ID-displayed numbers) call into our office, the receiver's phone "blips" with a partial ring, then the caller receives a fast busy. Debugging on the Tenor shows that the PBX is dropping the call due to "Invalid information element contents." With the Tenor out of the loop, these calls come through fine.
The Tenor can be configured to pass a preset number for caller ID. When we do this, the following happens:
- we force the caller ID number to a valid 10-digit phone number (e.g.4035551234) and ALL calls, including caller ID-blocked calls, come through.
- we force the caller ID number to nothing (empty string) and NO calls, including calls which display caller ID numbers, come through.
- we force the caller ID number to "4" and ALL calls, including caller ID-blocked calls, come through.
I have been assured by two different "PBX guys" that the Norstar is completely indiscriminate about caller ID. It shouldn't care what it is being given, but I think our tests have proved very clearly that it does care, and if it's getting "nothing" (i.e. the caller ID number is blocked or we force it to an empty string), the PBX is choking on "Invalid Information Element Contents" and not accepting the call.
Any thoughts from someone more knowledgeable on Quintum/PBX/PRI/ISDN/telec
om than me?