MERMAIL: Best Option to ring MCR then revert to Auto Attendant? 2

[x11dude]

Hi again all,

I'm using Meridian Mail and looking for your favorite solutions for the following:

Incoming calls to a store go to an Auto Attendant (Phantom DN, 500). One AA option (if selected) rings all store phones simultaneously (on an MCR DN).

Store manager would rather calls come directly to store phones then forward to the AA if not answered.

Should I set up the incoming DN as a phantom with an option to revert to the AA? Can one phantom revert to another phantom?

Or is there a better way to do this? Many thanks in advance!

Option11: ver 2111 rel 24 issue 24

Best,
x11dude

 

[PRI265]

Well, it seems there's 2 things to look at: How does the incoming call reach the AA, and what is the no-answer current option on the store's MCR DN?

If you know how the incoming call reaches the AA, then just change it to go to the existing MCR rather than to the AA. It might be an incoming digit conversion setting in LD 49. And then look into the existing MCR to see which appearance has the "MARP" ownership, and change it so that the FDN (forward-no-answer) goes to the AA, and also make sure that the MARP'ed TN has a CLS of FNA (forward-no-answer-allowed) as well. (You might want to also change the HUNT to go to the AA, too, in case all MCR lines are busy.)

I would alter the no-answer option first and test it to make sure that unanswered calls roll into the AA okay, and then change the incoming call to go to the MCR.

Hope this helps and not hinders.

 

[x11dude]

Hey there PRI - thanks for your quick response! (I love this forum!)

Currently incoming calls go right to the AA DN (phantom). Store calls that aren't picked up go to VM; offhand I can't recall how I set it up - so I'm going to need to commune with the system a while for the details...

Brilliant idea to HUNT to the AA, by the way. I would've spaced that for sure!!

It may be a couple days before I can get down there and look up the details; I may post the output here if I have questions (which, knowing me, is likely, lol!)

Thanks again so much!
-x11dude

 

[PRI265]

If the incoming call goes directly to the AA, then do people just dial a DID number? Sorry, x11dude, but I'm trying to remember how the phantom 500 line would work with an auto-attendant.

 

[x11dude]

Lemme think, good question. Incoming DID does go right to the AA. That particular DID's TN is on TN 61 2. Then in Mermail the DID is the AA. THat part works fine.

How do you normally set it up - anything different I should look at? (I'm open to ideas!)

I'll pull up specifics; will take a couple days.

Thanks again! I'll check your posts early next week if not sooner!

regards,
x11dude

 

[bignose21]

Remove the Phantom that you use for the AA.

Put in a LIN Hunt Group with the AA number as the PLDN

In Hunt group first Choice the MCR Key Second Choice the Mail DN.

 

[x11dude]

Great feedback, thanks!

As this will be setup differently than our other AAs - I'll have to do some poking around as to which loads to use. Is this all in LD 18 - or 56 / 57 or ?? (sorry but I don't use those loads much).

Of course I'll take a PBX backup first!

I probably should ask too: as PRI265 was surprised by the way our AAs were defined (as phantoms) - would bignose's way be more standard? Just curious....I wonder if whoever set ours up just had taken a shortcut. If there are better ways I'm always open to them.

Thanks again, you both have been a GREAT help!

x11dude

 

[bignose21]

No Phantoms are quite ok for getting to Mail/Callpilot applications can also use CDN with DCFW to Mail DN or ACD with NCFW to mail DN (I think all would work).

I was just coming up with a solution for you wanting to go to a set then AA, most places just main number straight to AA.

 

[x11dude]

Cool, thanks! Yes I know, setup is somewhat odd (ring then AA) - it's kinda like an "answering machine" setup(!) - but hey that's what the boss wants, lol!

BTW: Your recommendation (LIN Hunt Group with the AA number as the PLDN - In Hunt group first Choice the MCR Key Second Choice the Mail DN.): Which loads are used - is it LD 18, 56, 57 or other(?) - I've never had to set up a hunt group here...thanks in advance!

Many thanks, this forum ROCKS!

x11dude

 

[bignose21]

LD 18
REQ new
Type GHT
LSNO X (List number this can be 0-254 just cannot clash with
other Hunt Groups or Speed Call Lists)
CUST 0
DNSZ 4 (Length of DN's)
SIZE 2 (Number of entries in the hunt group)
STOR 0 XXXX (0 is the store number XXXX is the number of the MCR)
WRT <enter>
STOR 1 XXXX (XXXX is you Voicemail DN)

enter all the way out.

LD 57
REQ CHG
TYPE FFC
CUST 0
CODE PLDN
PLDN XXXX (PLDN Number what your phantom used to be)
USE GPHT
LSNO X (The GHT List Number created above)
HTYP LIN (Linear hunt group)
CFWI <enter> (You can change this to yes if you want the call
presenting even when the user has a call forward on)
MQUE xxx (Number of calls to Queue this can be a number or ALL, 0
means no calls queue)

 

[x11dude]

Doggoneit that's beautiful!

Thanks, a HUGE help and just what I needed. I'll give'r a go later!

Best regards,
x11dude

 

[x11dude]

Hi again,

Prior to doing LD 18 and new'ing the GHT (as described above), I went into ld 20 to first print GHTs that might be in the system. Received "SCH8894 FNP package is not equipped."

Does this mean I can't do the option we discussed? (Following is from LD 22) - thanks in advance!

REQ prt
TYPE pkg
OPTF 1
CUST 2
CDR 4
CTY 5
RAN 7
TAD 8
DNDI 9
EES 10
INTR 11
ANI 12
ANIR 13
BRTE 14
DNDG 16
MSB 17
SS25 18
DDSP 19
ODAS 20
DI 21
DISA 22
CHG 23
CAB 24
BAUT 25
BQUE 28
NTRF 29
NCOS 32
CPRK 33
SSC 34
IMS 35
UST 35
UMG 35
ROA 36
BACD 40
ACDB 41
ACDC 42
LMAN 43
MUS 44
ACDA 45
MWC 46
AAB 47
GRP 48
NFCR 49
ACDD 50
LNK 51
FCA 52
SR 53
AA 54
HIST 55
AOP 56
BARS 57
NARS 58
CDP 59
PQUE 60
FCBQ 61
NAUT 63
SNR 64
HOT 70
DHLD 71
LSEL 72
SS5 73
DRNG 74

PAGE 001

PBXI 75
DLDN 76
CSL 77
OOD 79
SCI 80
CCOS 81
CDRQ 83
TENS 86
FTDS 87
DSET 88
TSET 89
LNR 90
DLT2 91
PXLT 92
SUPV 93
CPND 95
DNIS 98
BGD 99
RMS 100
MR 101
AWU 102
PMSI 103
MCT 107
ICDR 108
APL 109
TVS 110
TOF 111
IDC 113
AUXS 114
DCP 115
PAGT 116
CBC 117
CCDR 118
EMUS 119
SCMP 121
FTC 125
BKI 127
DTI2 129
TBAR 132
ENS 133
FFC 139
DCON 140
MPO 141
ISDN 145
PRA 146
IEC 149
IAP3P 153
PRI2 154
ACNT 155
THF 157
FNP 160
SAR 162
LAPW 164
GPRI 167
ARIE 170
CPGS 172
ECCS 173
AAA 174
EOVF 178
HVS 179
DKS 180

PAGE 002

SACP 181
EDRG 185
POVR 186
SECL 191
AINS 200
IPRA 202
XPE 203
XCT0 204
XCT1 205
MLWU 206
HSE 208
MAID 210
VAWU 212
BRI 216
IVR 218
MSDL 222
FC68 223
SSAU 229
BRIT 233
FCDR 234
BRIL 235
MCMO 240
MULTI_USER 242
ALRM_FILTER 243
VMBA 246
CALL ID 247
DPNA 250
SCDR 251
PHTN 254
ADMINSET 256
ATX 258
NI-2 291
MAT 296
MQA 297
CPP 301
CPCI 310
TATO 312
OPEN ALARM 315
NGEN 324
RANBRD 327
MUSBRD 328
ESA 329
NI-2 CBC 334
MC32 350
DBA 351
FDID 362
NMCE 364

REQ
TIM609 11:00 8/8/2011 CPU 0

 

[bignose21]

This is from the RLS 25 manuals (Oldest I had), and it looks like you are missing packages.

Feature packaging
For markets other than France:
Group Hunt/DN Access to SCL (PLDN) package 120.
Dependencies:
• International Supplementary Features (SUPP) package 131
• Flexible Feature Codes (FFC) package 139, and
• System Speed Call (SSC) package 34.
For the French market only:
French Type Approval (FRTA) package 197; and Group Hunt/DN Access to
SCL (PLDN) package 120.
Dependencies:
• International Supplementary Features (SUPP) package 131
• Flexible Feature Codes (FFC) package 139, and
• System Speed Call (SSC) package 34.

 

[x11dude]

Yep that kinda confirms things... can't do Group Hunt.

As a general rule, I'm still amazed by what this old system CAN do.

Thanks for the response; I guess we'll just get by till I replace this system (ver 2111 rel 24 issue 24). I have another thread going about potential replacements; interesting...

regards,
x11dude

 

[bignose21]

You could just IDC straight to your MCR key then the MARP Set can forward no answer to the AA (Number for the AA in the Mail would match the MCR DN).

You can alter the RCO value (0,1 or 2) against the MARP Set which refers to the CFN (0,1 or 2) and DFN (0,1,or 2) for the number of rings before forwarding.

 

[x11dude]

Hi Bignose21,

Aaaack, sorry - lost me a little. I haven't had to set up an IDC, in fact (in LD21) I see IDCA is NO.

I've searched threads - but I'm still confused re night-time (or not), and, once I enable IDC, what data gets converted? And are the RCO, CFN and DFN values all for the MCR's MARP as defined in LD20?

If you have any syntax examples, that would be great! (Sorry to be so needy here - blazing new territory - but your feedback welcome!)

Many thanks!
-x11dude

 

[bignose21]

For the MARP bit just LD 20
REQ prt
TYPE dnb
CUST 0
DN <MCR DN>

The TN with MARP against it is the one that controlls the forwards.

LD 15 (Printed in 20) in the RDR data you set the number of ring cycles before forwarding. So what I normaly do as RCO 0 is assigned against every set by default you would set the CFN0 and DFN0 to a standard for all normal sets (I normaly use 4 rings). Then I increase for other users so you might say that an RCO 1 is equal to 6 rings and RCO 2 to 8 rings. for this in RDR you set:

CFN0 4
CFN1 6
CFN2 8

DFN0 4
DFN1 6
DFN2 8

Then against your set if you want to extend the waiting period before Call Forward you just alter the RCO value of that set.

If you are not currently using IDC no need to start just make the MCR keys what your Phantom used to be.

 

[x11dude]

Nice! Thanks! I been cabling today (exhausted!) - will try this on Monday!

regards,
x11dude