Hunting status

[nanningmiss]

Our system was upgraded to CS1000E RLS 6.0 recently.

Before the upgrade, when I called an extension, I knew if the called party is on phone, because my phone showed its hunting to key 1 (Hxxx "B") when key 0 is busy.

After the upgrade, when key 0 is busy, the hunting status doesn't appear anymore. So I don't know if the called party's key 0 is busy.

Is this a change at FTR_DATA? Any idea would be greatly appreacated. Thanks in advance.

 

[BillCorv]

You might check your LD 95 CPND data block.
Reason for forwarding and displays are programmed there.

 

[johnpoole]

and there is a new prompt in the cdb that turns that on and off.. do not have my feature discript disk here at home, but it's a quick read. after you change (or check) the cdb opt, then the ld 95 prt cpnd will show you where to add hunt to the display list

john poole
bellsouth business
columbia,sc

 

[nanningmiss]

Thanks for the reply, BillCorv and John.

I did some change at LD 95 like this:
TYPE CPND
CUST 0
CNFG ALON
MXLN 24
STAL YES
DFLN 13
DES NO
RESN YES
CFWD F
CFNA N
HUNT B
PKUP P
XFER T
AAA A
ECSL

NITC NI

Basically, the setup now is the same as before upgrade. Now the called party shows the hunting info but the calling party doesn't. Interesting... the calling party needs this feature...

 

[johnpoole]

since your ld 95 looks good, you get to find the new prompt well hidden in the cdb.. start by looking for new opt's under either ftr data or att data...

even not using 2250 consloes, the att data still has to be right..

your looking at either a new gate opener for that rls or a patch.. the patch is not on site YET, and your the only end user that i can find so far with this issue... i would bet on a new cdb option..

john poole
bellsouth business
columbia,sc

 

[nanningmiss]

Thanks again John.

Our vendor updated patches for an upgrade problem. So I think this problem is not related to a patch but a gate opener.

Hopefully, someone encounters this before. Here is my FTR_DATA:

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 CFRD
COX CPA CTD DBD DNX DSX
HTU HVD IBL IC1 IDP XLF
IHD XTG FKA LOA LRA MCI
MWUD PVCD REA RND
RTR RTA ROX SBD SYD
TTAD VOBD CWRD HLPD HRLD
CXOA
DGRP 100
IRNG NO
PKND 1
DNDL NO
SPRE 88
PREO 1
BPSS NO
SRCD 0000
EEST NO
EESD NO
TTBL 0
MUS NO
ALDN
RECD NO
PORT 0
STCB NO
NSCP 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 000
FXS NO
DFLT_LANG ENG
STS_MSG
MSG01 Please leave message
MSG02 Back to work
MSG03 In a meeting
MSG04 On a conference call
MSG05 At lunch
MSG06 Busy call
MSG07 Out of the office today
MSG08 On a business trip
MSG09 Project deadline today
MSG10 Will reply after
VO_ALO NO
PCA ON
TPDN
BFS_CFW YES
VO_CUR_ZONE_ZDM NO
VO_CUR_ZONE_TD NO


PAGE 002

ZBD NO

 

[nanningmiss]

At the old PBX, hunting status can be showed at the calling party. Here is the FTR_DATA of the old PBX:

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 CFRD
COX CPA CTD DBD DNX DSX
HTU HVD IBL IC1 IDP XLF
IHD XTG FKA LOA LRA MCI
MWUD PVCD REA RND
RTR RTA ROX SBD SYD
TTAD VOBD CWRD HLPD HRLD
CXOA
DGRP 10
IRNG NO
PKND 1
DNDL NO
SPRE 88
PREO 1
BPSS NO
SRCD 0000
EEST NO
EESD NO
TTBL 0
MUS YES
MUSR 27
ALDN
RECD NO
PORT 0
STCB NO
NSCP 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 000
FXS NO
DFLT_LANG ENG
STS_MSG
MSG01 Please leave message
MSG02 Back to work
MSG03 In a meeting
MSG04 On a conference call
MSG05 At lunch
MSG06 Busy call
MSG07 Out of the office today
MSG08 On a business trip
MSG09 Project deadline today
MSG10 Will reply after
VO_ALO YES
VO_ALOHR 0
PCA ON
TPDN

I can't see many differences.

Thinking out loud... The hunting status can be showed at the called party, but not at the calling party. It could be the signalling setup... I will have a look at EM.

 

[nanningmiss]

Update:

I did more test calls and found that this feature only worked for the inter-PBX calls.


Before upgrade:
The complaint was from a receptionist at a branch office. She had an M2616 digital phone while almost all other phones were IP phones. All these IP phones redirected to the main office. So any call from that M2616 to an IP phone was an inter-PBX calls.

After upgrade:
The brach office was cut over to a SMG. So a call from that M2616 to any IP phone becomes an internal call.


Test calls:
The old PBX (the main office) is still in use. So I can still make test calls from and to it.

Any call between the old PBX and the new one (CS1000E) (both directions) can show the hunting status.

Any internal call (within the old PBX or within CS1000E) can NOT show the hunting status.


I am afraid that the receptionist may lose this feature for good.