I'm having an issue with my customer's telephony provider about 2B-Transfers over an ISDN line with the NI2 protocol variant.
They have a Meridian PBX with a T1 PRI to the IVR server. I can answer the incoming calls and perform outgoing calls. I can even perform channel switching to establish "transfers" (conference calls, actually) and they work just fine.
However our customer really wants the 2B-Transfer functionality, so as to leave as much channels as possible for incoming calls, considering the call volume they have.
Currently, their T1 is divided as 12 channels for incoming calls, 11 for outgoing/switching and just 1 for outbound faxes (on demand).
They need to leave at least 17 channels for incoming calls, 3 for 2B-Transfers and 3 (at most) for outbound faxes.
I had been explaining the 2B-Transfer mechanism for almost 2 years now, but they seem to not understand it... I'm almost sure they don't support it, but our customer insists it's the exact way the call transfers should work, so I've been trying to pursue it...
The telephony provider just handed me the Meridian's transfer mechanism (attached PDF) which to me seems more like a channel-release mechanism after a transfer is made. Please, read it and tell me if this is familiar to you.
At this point I'm willing to handle my customer a formal spec about 2B-Transfers (tech requirements, pre-requisits, mode of operation/invocation involving the CRVs, expected results after invocation, etc.), but I don't have any... Do you?
My intention is to give this to our customer so they can handle it to their telephony providers, so they can start to search for a similar mechanism on their Nortel/Meridian documentation... They may even know about it by other name!
I appreciate any formal documentation about 2B-Transfers you may have.
| Attachments: |
 Meridian's TAT.pdf [17.58 KB]
Downloaded 1119 times |
. However, your client's telco should have access to that information.