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!

Confusion with Call Park and MCR (??) 3

Status
Not open for further replies.

x11dude

IS-IT--Management
Nov 22, 2010
153
US
Hi all!

In addition to the 50 or so phones we already have... we are opening a new retail store. It's in the same building, using the same Meridian Option11 we've always had. 6 phones in the store all ring simultaneously (MCR). Any phone can answer the main DID number. I also have PRK buttons programmed(among others).

The problem comes when a user wants to "park" a call and pick up at another location (say, to check stock on hand). She is unable to do so - and has to return to the first phone to answer the caller.

What am I missing? Is PRK the wrong solution here?

Many thanks in advance!
x11dude
 
Call Park is programmed in LD 50. It's function is usually in conjunction with a paging system.

Call Park is used with a FFC and it would be assigned a number in the range specified in LD 50. i.e. 1800 to 1819.

It's a case of using the FFC followed by the number that it was parked against.

I don't know of many customers that uses it. If you have enough digitsl sets, then MCR's are a better option, but there are restrictions on the number of keys that can be assigned to the same MCR.


All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
I guess you are saying that you are trying to park an mcr call?
 
Thanks for your response! I'm still missing something though.

I guess I should get deprogram PRK - but the MCR on the other phones stops blinking. What's a better way of picking up the same call from another phone?

Thanks,
x11dude
 
(and yes Ricky - we were trying to park an MCR call. Not good, I take it(?) Better solutions very much appreciated...)
 
Park is ok. The person that parks the call need to inform whoever they want to pick the call up where it is parked.

Calls can be parked to a system dn or a telephone dn. The way we use it is feature code 171+ the telephone dn to park the call and feature code 172+ the telephone dn to retrieve the call. A park key is your feature code.

Print your feature data and verify you have cpa which is call park allowed. Then print the park data block in ld 50. This where you define system dns. I find it easier to park a call to a telephone dn.
 
Hi again Ricky,

Wow, there's more to this than I realized. Can you think of a simpler way - say, if a person is just walking to another phone, to pick up that phone and retrieve the same call?

I've never actually set up a park data block. If there's an easy alternative, I'm all ears.

If I do need to go that route (park data block) - do you just set up a dummy DN to assign it to? (Which also leads me to wonder - do we need to assign more than one?)

Many thanks for your help, I really appreciate it!
 
Call Park is easy
Ld 50
decide on a start digit exapmle (ext 100)
decide on how big of a block you want (10) "how many calls you can park"
add park to your sets
test it make a call and use Park button, system gives you code (100)
go to any phone and dial 100.
 
You can always make the keys scr with multiple hunt keys. I wouldn't go that route though. Park is cleaner and easier.
 
Thanks Ricky - I will get Park going today! First time in LD 50, wish me luck - I'm going in! :)
 
OK I think I'm ready for the next step. I have the Park DNs (which were already in the system). I have sets with PRK keys defined. But I am missing something. Do I have enough programmed into the system to actually use the keys? (and do I have enough info to explain to the users how to use the feature?)

Any help appreciated. Here's some pertinent overlay information from LD 21, 20 and 50 - please let me know if you need more info!

Many thanks! - here are the printouts:

>ld 21
PT1000

REQ: prt
TYPE: ftr
TYPE FTR_DATA
CUST 0

TYPE FTR_DATA
CUST 00
TBL
**DAPC**PREFIX TABLE NO: 00 **
UNKN**INTL**NATL**ESPN**LOCL**ELOC**ECDP**
UNKN*
E164* 00 0
PRIV*
E163* 00 0
TELX*
X121*
NATL*

OPT AHD BIND BIXA BLA CFF CFRA
COX CPA CTA DBA DNX DSX
HTU HVD XBL IC1 IDP XLF
IHD ITG FKA LOA LRA MCI
MWUA PVCD REA RND
RTR RTD ROX SBD SYA
TTAD VOBA CWRD HLPD HRLD
CXOD
DGRP 5
IRNG NO
PKND 2
DNDL NO
SPRE 8888
PREO 0
BPSS NO
SRCD 1234
EEST NO
EESD NO
TTBL 0
MUS YES
MUSR 3
ALDN
RECD NO
PORT 0
STCB NO
MCDC NO
NAUT NO
IDEF NO
MTAR NO
LEND NO
MSCD NO
CPCI NO
CONF_DSP
CNFFIELD NO
CNF_NAME CONF
INTFIELD NO
INT_NAME I
EXTFIELD NO
EXT_NAME E
BSFE NO
ASPCT 010

REQ:

>ld 20

PT0000
REQ: prt
TYPE: dnb
CUST 0
DN 2300
DATE
PAGE
DTC103

DES

DN 2300
TYPE PARK


NACT
REQ:
REQ PRT
TYPE:
TYPE DNB
CUST 0
DN 230
DATE
PAGE
DES

DN 2300
TYPE PARK

DN 2301
TYPE PARK

DN 2302
TYPE PARK

DN 2303
TYPE PARK

DN 2304
TYPE PARK

DN 2305
TYPE PARK

DN 2306
TYPE PARK

DN 2307
TYPE PARK

DN 2308
TYPE PARK

DN 2309
TYPE PARK


NACT


>ld 50
S1FEA000
MEM AVAIL: (U/P): 1339260 USED U P: 73670 45245 TOT: 1458175
DISK RECS AVAIL: 441
REQ prt
TYPE cpk
CUST 0

CPTM 120
RECA NO
SPDN 10 2300
MURT 3

MEM AVAIL: (U/P): 1339260 USED U P: 73670 45245 TOT: 1458175
DISK RECS AVAIL: 441
REQ
 
Hi again all,

Just an update. I do have Park working now. One problem is that if I'd been smarter (!) I would've started with display sets sooner!

I have Park working but it's to 4-digit extensions. I may try to set it up to 2-digit numbers to make it a bit easier on the users.

Thanks again all for all your help! Great forum!
 
Hi Ricky, curious: why keep it 4 digit? Turns out I had a range of DNs from 80-87 available. My users aren't happy with the Meridian system as it is (perhaps understandably) and I wanted to keep it as easy as possible for them.

Anyway yesterday I OUTed the 4-digit Park range and park'd the new 80-87 range. Worst part was trying to scare up a few display 2008 sets.

Hope I didn't hose things too bad. And thanks for all your help! - if I absolutely need to switch back, I now know how -I can do so easily! (Except for having to re-train my users, lol)

Best,
x11dude
 
I just don't like to tie up blocks of numbers. By using 80 for example there is no way to use 8000 through 8099. But if the system is small I guess it doesn't really matter. Main thing is you made the users happy. And you did a fine job of implementing the park feature.
 
Aha, you are right, I never thought about that (tying up the entire block of 8000s). Our system is fairly small (50 - 60 sets) and we do have a good block of the 70s available (71 - 78 as I recall).

It's my hope that (as we grow) we could (maybe) afford a newer phone system anyway....

Thanks again,
-x11dude
 
Call park is probably not any simpler on another phone system - unless you want to skip your landline phones and go all mobile ;-)
 
Probably right re call park on a newer system. I might set up an analog cordless phone for one of our users in the store (just as an option). I don't think all mobile would work for us though (as we use MCR - customer call-in lines, auto attendant, etc.)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top