Using CallPilot as a VM for a Mitel sx2000

[chrisay59]

Guys I'm at my wits end. I have a CS1000E/T combination running Rls 4.5, I have a Callpilot Rls 4 on the E. My task has been to configure 4000 mailboxs on the CP, however the extensions exist on the Mitel SX2000. My problem is that I ca express message to these VM Boxes and I get my MWI back on the Mitel Handset but I CAN NOT get CP to recognise when a Mitel Ext is diverted to it that it should go into the appropriate VM Box. All I get is "Callpilot, from Nortel Networks, Mailbox?" Any help would be greatly appriciated.

Thanks

 

[johnpoole]

your interface between the rls 4.5 and the mitel? i've got that to work with qsig pri's BUT i had to network the switches to dial the actual ext number.. prior to that networking users dialed 7 plus the ext from the sl1 to the mitel,,, and 6 plus the other direction.. once i built the mitel exten's as dsc's the rest feel into place.. in that case the customer went to all 5 digit dialing, mostly due to their did ranges.. i could have kept 4 digit but would have had a few hundred stations to change the dn on due to conflicts.. the trouble with that one was one switch was 437 2000 to 4000 the other 736 3000 to 7000... the over lap forced 5 digit...

without qsig and a clean network, forward between the two went to "mailbox? prompt"

john poole
bellsouth business
columbia,sc

 

[chrisay59]

John, the customer is using 5 digit dialling across their network (12500 Exts) the link between the Mitel and Nortel is QSIG (going via a SX3300 because the sx2000 can't take an QSIG links so the 33000 is doing the conversion) I can dial the Mitel extension fine and they can dial the Nortel exts fine, using DSCs, I just can't get CP to recognize that the Mitel Exts are VM Boxes.

 

[chrisay59]

This is a print out of my DCH, my QSIG Route, my Trunk members and the messaging I get when I make a call from the CS1000E (Ext 22890) and the Mitel (Ext 22803), the CP SDN is 22111.


REQ prt

TYPE adan dch 14

ADAN DCH 14
CTYP MSDL
CARD 01
PORT 1
DES QSIG
USR PRI
DCHL 1
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ISGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
Rlld LS ID 4
QCHID YES
RCAP COLP PRI DV3I QMWI
PR_TRIGS DIV 2 3
CNG 2 3
PR_RTN NO
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7

REQ: prt
TYPE: rdb
CUST 0
ROUT 14
TYPE RDB
CUST 00
DMOD
ROUT 14
DES QSIG
TKTP TIE
NPID_TBL_NUM 0
ESN NO
RPA NO
CNVT NO
SAT NO
IDEF NET
RCLS INT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC ISGF
SBN NO
PNI 00001
NCNA NO
NCRD NO
CTYP CDP
INAC NO
ISAR NO
CPFXS YES
DAPC NO
INTC NO
DSEL VOD
PTYP DTT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 6014
TCPP NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
SIGO STD
MFC NO
ICIS YES
OGIS YES
TIMR ICF 1920
OGF 1920
EOD 13952
LCT 256
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896
GTI 896
SFB 3
PRPS 800
NBS 2048
NBL 4096
IENB 5
TFD 0
VSS 0
VGD 6
DTD NO
SCDT NO
2 DT NO
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS NO
PANS YES
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TTBL 0
ATAN NO
PLEV 2
OPR NO
ALRM NO
ART 0
PECL NO
DCTI 0
TIDY 6014 14
SGRP 0
ARDN NO
AACR NO

REQ: prt
TYPE: tnb
TN 1 1
DATE
PAGE
DES QSIG
TN 001 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI2
PDCA 1
PCML A
NCOS 7
RTMB 14 1
B-CHANNEL SIGNALING
TGAR 1
AST NO
IAPG 0
CLS UNR DIP WTA LPR APN THFD XREP BARD
P10 VNL
TKID
AACR NO

TN 001 01 MBER 1 QSIG
TN 001 02 MBER 2 QSIG
TN 001 03 MBER 3 QSIG
TN 001 04 MBER 4 QSIG
TN 001 05 MBER 5 QSIG
TN 001 06 MBER 6 QSIG
TN 001 07 MBER 7 QSIG
TN 001 08 MBER 8 QSIG
TN 001 09 MBER 9 QSIG
TN 001 10 MBER 10 QSIG
TN 001 11 MBER 11 QSIG
TN 001 12 MBER 12 QSIG
TN 001 13 MBER 13 QSIG
TN 001 14 MBER 14 QSIG
TN 001 15 MBER 15 QSIG
TN 001 16 MBER 16 QSIG
TN 001 17 MBER 17 QSIG
TN 001 18 MBER 18 QSIG
TN 001 19 MBER 19 QSIG
TN 001 20 MBER 20 QSIG
TN 001 21 MBER 21 QSIG
TN 001 22 MBER 22 QSIG
TN 001 23 MBER 23 QSIG
TN 001 24 MBER 24 QSIG
TN 001 25 MBER 25 QSIG
TN 001 26 MBER 26 QSIG
TN 001 27 MBER 27 QSIG
TN 001 28 MBER 28 QSIG
TN 001 29 MBER 29 QSIG
TN 001 30 MBER 30 QSIG


DCH 14 UIPE_OMSG CC_SETUP_REQ REF 000001D3 CH 1 30 TOD 14:39:16 CK EFF94974
PROGRESS: CALL IS NOT END TO END ISDN
PROGRESS: INTERWORKING WITH PRIVATE WORK
CALLING #:22890 NUM PLAN: PRIVATE TON: ESN CDP
CALLED #:22803 NUM PLAN: PRIVATE TON: ESN CDP

DCH 14 UIPE_IMSG CC_PROCEED_IND REF 000001D3 CH 1 30 TOD 14:39:16 CK EFF94AFC

DCH 14 UIPE_IMSG CC_SETUP_IND REF 00000180 CH 1 29 TOD 14:39:16 CK EFF94C0A
CALLED #:22111 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:22890 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 14 UIPE_OMSG CC_PROCEED_REQ REF 00008180 CH 1 29 TOD 14:39:16 CK EFF94C85

DCH 14 UIPE_OMSG CC_ALERT_REQ REF 00008180 CH 1 29 TOD 14:39:16 CK EFF94FD8
PROGRESS: CALL IS NOT END TO END ISDN
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 14 UIPE_IMSG CC_PROGRESS_IND REF 000001D3 CH 1 30 TOD 14:39:16 CK EFF95096
PROGRESS: CALL IS NOT END TO END ISDN

DCH 14 UIPE_IMSG CC_ALERT_IND REF 000001D3 CH 1 30 TOD 14:39:16 CK EFF950A4
PROGRESS: CALL IS NOT END TO END ISDN

DCH 14 UIPE_OMSG CC_SETUP_RESP REF 00008180 CH 1 29 TOD 14:39:16 CK EFF952AE
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 14 UIPE_IMSG CC_SETUPCOMP_IND REF 00000180 CH 1 29 TOD 14:39:16 CK EFF952E7

DCH 14 UIPE_IMSG CC_SETUP_CONF REF 000001D3 CH 1 30 TOD 14:39:16 CK EFF9538A

DCH 14 UIPE_OMSG CC_DISC_REQ REF 000001D3 CH 1 30 TOD 14:39:18 CK EFF96322
CAUSE: #16 - NORMAL CALL CLEARING

DCH 14 UIPE_IMSG CC_RELEASE_IND REF 000001D3 CH 1 30 TOD 14:39:18 CK EFF963E0

DCH 14 UIPE_OMSG CC_RELEASE_RESP REF 000001D3 CH 1 30 TOD 14:39:18 CK EFF963E9

DCH 14 UIPE_IMSG CC_DISC_IND REF 00000180 CH 1 29 TOD 14:39:18 CK EFF963F8
CAUSE: #16 - NORMAL CALL CLEARING

DCH 14 UIPE_OMSG CC_RELEASE_REQ REF 00008180 CH 1 29 TOD 14:39:18 CK EFF96402

DCH 14 UIPE_IMSG CC_RELEASE_CONF REF 00000180 CH 1 29 TOD 14:39:18 CK EFF96447

 

[MagnaRGP]

As a test, set up a mitel ext to forward no answer to a display set on the Nortel and see what you have. If the display reads ****-** H**** then the call pilot is not seeing the DN which is RNAing to it and therefore does not know what to do with the call. You'll need to troubleshoot the networking more.

Do the same test on a Nortel phone and your display should read XXXX YYYY "CFWD" -- where XXXX = the calling DN, YYYY = the called DN (or something like that). Your calls from the Mitel will need to be forwarded such that that info propagates to the Nortel and CallPilot.

I know nothing (they call me Schulz) about QSig, so that about wraps up my 2 cents Canadian.