Archive for the ‘MLPP’ Category

MLPP – Alternate Party Settings

Posted: June 3, 2006 by cciestudy in MLPP

Alternate Party Settings take effect only on the first hop of Call forward Busy and NoAnswer. This does not apply to Call Forward All

Example:
Extension 7500, CFNA/CFB set to 7501
Call forward No Answer timeout set to 20 seconds
Alternate Party Destination set to 7510
Alternate Party No Answer Timeout set to 10 seconds
Call waiting disabled by setting busy trigger to 1
If a MLPP call comes to 7500 while it is busy/no answer, the call will ring 7501 for 10 seconds (Alternate Party No Answer timer). If 7501 does not answer, the call will forward to 7510 (APD)

Advertisements

MLPP on gateways

Posted: June 3, 2006 by sankar in CM4.1 Features, MLPP

** MLPP settings does not work on FXO gateways.

** MLPP does work on gateways with T1 PRI and CAS (MGCP).

** No support for MLPP in H323 gateways. But on a ICT you will see a setting for Premption Indication. A trunk itself cannot be Prempted, so there is no way to enable Premption on an ICT. The premption indication on a ICT, helps in passing MLPP indication when a precedence calls is placed from one CM Cluster to another CM cluster.

Sample lab for MLPP testing on gateways: 

1. Set the gateway with MLPP Indication enabled and MLPP Premption enabled. Setup 1026 and 1027 with capability to call Exec override and Flash override respectively.

2. Set up a route pattern 9.@ in Exec partition with Exec override settings

3. Set up a route pattern 9.@ in Flash partition with Flash override settings

4. Point both 9.@ patterns to the MGCP T1 gateway. Busy out all channels except 1 channel. MLPP works only when the trunk is busy. Use B channel maintenance to do this.

5. Place a flash override call from 1027 and then place a exec override call from 1026. The call to 1027 is disconnected and the call from 1026 is connected to the dialed.

6. Place a exec override call from 1026 and then place a flash override call from 1027. The call to 1027 will not succeed and a Block Premption  Announcement is heard. "A equal or higher precedence call has prevented the completion of the call. Please hangup and try again later. This is a recording"

MLPP

Posted: June 3, 2006 by sankar in Cisco General, CM4.1 Features, MLPP

How to setup basic MLPP ?

a. Take three phones 1025, 1026 and 1027. Let 1025 be the destination phone. 1026 be able to make Exec Override calls. 1027 be able to make Flash Override calls.

b. Set them all up in same MLPP domain 000011 (for ex:)

c. Set 1025 with MLPP indication enabled, Premption – Forceful

d. Set 1026 and 1027 with MLPP indication enabled, Premption – Can be disabled. No need to set them to forceful.

e. Create translation pattern 90.1025 in partition Exec and set the MLPP setting to Executive Override. This TP can be accessed only by 1026. Translate 90.1025 to 1025.

f. Create translation pattern 90.1025 in partition Flash and set the MLPP setting to Flash Override. This TP can be accessed only by 1027. Translate 90.1025 to 1025.

g. Place a flash override call from 1027 to 1025. (Dial 90.1025 from 1027.). You should note a different ring tone on 1025 and also a precedence ringer display.

h. Place a exec override call from 1026 to 1025 (Dial 90.1025 from 1026). You should immediately hear a precedence tone on 1025 and 1027. (Continous tone). Both parties 1025 and 1027 have to independently hangup. The Exec override call from 1026 is offered to 1025. Phone 1025 starts ringing.

i. If 1025 doesnt answer the exec override call from 1026, after 30 seconds, the call between 1025 and 1027 is dropped and the exec override call from 1026 is offered to 1025.

j. A flash override call cannot preempt a exec override call. If 1026 and 1025 are in a exec override call, a flash override call from 1027 cannot preempt the call between 1026 and 1025, as the flash override call has lower precedence. The flash override call will appear as call waiting on 1025. (No call waiting beep is heard).

k. An exec override call cannot preempt another exec override call (same domain), unless the service parameter Exec Override Call Preemptable is set to true. With the default setting (false), if 1026 places an exec override call to 1025, and 1027 places an exec override call to 1025, this call will appear as call waiting on 1025. (No call waiting beep is heard).

l. Do not set Preemption enabled to Forceful and Premption indication to Off of Default (If device pool is also off). This will prevent preemption on the destination device.

m. Only calls originating from devices in same domain can be prempted. If 1026 is set to domain 000011 and 1027 is set to domain 000022, 1026 cannot override 1027's call and vice versa.

n. If both 1026 and 1027 are set to flash override, One flash override call cannot preempt another flash override call. The call appears as call waiting (no beep is heard)