P to P T-l Console Forwarding & Appearances

[Sphoneman]

I am to be involved on one end of a Point to point T-l between 2MICS (6.1). I would set them up as as a CDP.

I have networked prior with a 3.0 & a 4.0

The question posed by the customer is to have the consoles at each end show the extensions on the CAPS/KIMS for Autodial DNs for all extensions in system "A" & "B".

Will I be able to call fwd from one console to the other by just F4 to the other console? They hand of the calls between the two sites through the day.

Steve
tele-dataservices.com

 

[aragon]

Yes you will be able to external call forward via destination code, you will want to use the MCDN keycode and enable TRO/TAT. You will also need to allow redirect in capabilities for any set that wishes to externally call forward.

You will not see a BLF for the remote site.
DSS keys for the remote site must be programmed via Feature*1 followed by the DN number in your CDP.
You can feature4 to the external autodial programmed to the DSS key via feature*1.

David Brillert

http://www.williamsglobal.com

 

[Sphoneman]

Thanks aragon,

That makes sense & did not think you could have the other sites extensions show staus.

The system "B" site is an existing Norstar being upgraded to 6.1 with a NAM.

My site is new with CallPilot.

They are keeping their Voicemails separate.

I don't think I would need the MCDN. Am I correct?

Steve
tele-dataservices.com

 

[hawks]

The MCDN keycode will be needed if you are connecting as PRI. You need the keycode for the SL1 protocol.

 

[aragon]

You will need MCDN for site to site PRI.
No MCDN = no SL1
No SL1 = no site to site networking

MCDN is also referred to as Advanced Private Networking when purchasing a keycode.

David Brillert

http://www.williamsglobal.com