Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

call forwarding (to cell phone) issue [ Partial Rerouting / Clip No Screening ]

Status
Not open for further replies.

teatreehs

Technical User
Jun 30, 2011
12
BE
Hi all,

the request sounded at first sight quite simple; so let's explain how it should work:

 User A and User C reside in the PSTN
 User B resides within the Mitel PBX
 User B activated a diversion (CFU, CFB, CFNR) towards User C
 CLIP (CLID) of the incoming call (User A or ‘Calling Party’) needs to be presented to the forwarding destination (User C)

Since the 'Clip no Screening' feature is not available due to country-specific regulations, the provider told me the only way to display the CLIP of User A (Calling Party) at User C is to use PR or 'parial rerouting', a standard ISDN supplementary service .

With PR configured at PABX side, the PABX signals to the network that the destination is forwarded to another number and it is the network that will setup a new call from A to C, he explains.

So far so good, can someone please tell me how I configure this in the Mitel ( MiVoice Business R.8 with E1 PRA) ?

Or - how do you usually handle such a requirement ??
Or - is possibly a workaround required ??

Thanks for your support !!
 
I think you might be hooped.

In North America, I believe what you are referring to is called Two B-Channel Transfer or Release Line Transfer
Help Files said:
Two B-Channel Transfer (TBCT; also known as Release Line Transfer) allows a MiVoice Business set user to transfer an external call to another external destination and have the two external parties connected through the trunks at the Central Office (CO) or SIP service provider. Because the calls are connected at the CO or SIP service provider instead of MiVoice Business, the incoming and outgoing trunks on MiVoice Business that would normally be required to connect the external parties are available for use.

TBCT is [highlight #FCE94F]supported[/highlight] for Bellcore and 5ESS variants of the [highlight #FCE94F]NI-2 protocol[/highlight] for the embedded ISDN offerings of MiVoice Business, as well as for SIP solutions. It is not supported on the NSU.

I don't see support for E1





**********************************************
What's most important is that you realise ... There is no spoon.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top