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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Nortel/Unity VM intgration & Keep Original Calling Party info on Xfer

Status
Not open for further replies.

lilabell

MIS
Apr 29, 2003
88
US
Hello folks of the forum I have an interesting problem that I would welcome any assistance on. Previously in what I like to call the good ol days we had an Octel 250 and a dirct xfer to VM ACD set up in the Option11 that was NCFW to the pilot for VM so if I am Joe Users admin and I have a call appearance for Joe on my phone I answer for Joe and let them know joe is unavailable. I xfer to the acdn that is ncfw to the pilot to vm and then enter joes extension complete the xfer and I go directly into Joes vm. If Joe gets the message he can reply to my message in the aria tui interface by pressing option 8 and replying to my message if the caller is internal .

Same applies in this new world of unity except this is what happens now. I am joes admin and I xfer the call directly into joes vm problem is the vm system thinks i called joe and if joe replies to the message I get the message instead original calling party - if the caller is internal it should not work for external calls.

I have a PIMG integration using a linear hunt. I followed the steps in the Unity (4.2) PMG integration guide and I have been over all of them. I can see in the unity tools that it thinks that it is capturing the extension of the person who transfered the call to vm instead of the calling parties ext. Cisco says that I dont have something configrued correctly in my PBX (Nortel Option11) to provide the extension of the calling party. I will be happy to provide that information but I dont know where to look if anyone has any idea what this might be caused by and can provide me with the LD # and syntax to provide this info as well as what I should be looking for that would be most appreciated. I think it is being sent because the config for the hunt is the same as it was in the Octel which worked but yet does not work with Unity?

Thank you,

Lilabell
 
cisco would blame that or any other problem they don't unerstand on nortel ( or anyone handy).. there great for data, they are pretty good voice, but none of there people have more then a few months experieice that i have met.. look at sfa/sfd in the class of both the original called and the transfer to ext.. it may not be the problem but if it's not, it's in the cisco.. there is not a place in the switch to send or screen the original dialed dn..

john poole
bellsouth business
columbia,sc
 
Do you have a PRI between the Unity and OPT11C? If you do here is the configuration for the PBX side: Just change MSDL to TMDI is using a TMDI card rest of the prompts from DES down are the same

DCH 56
CTYP MSDL
GRP 1
DNUM 4
PORT 0
DES CISCO
USR PRI
DCHL 56
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ISGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE NET
CNEG 1
RLS ID **
RCAP COLP NDI CCBI CCNI PRI DV3I CTI QMWI
PR_TRIGS DIV 2 3
CNG 2 3
CTR2 2 3
PR_RTN NO
MBGA NO
OVLR YES
DIDD 0
OVLS YES
OVLT 0
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
RDB:
TYPE RDB
CUST 00
ROUT 88
DES CISCO
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC ISGF
SBN NO
PNI 00001
NCNA NO
NCRD NO
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPFXS YES
DAPC NO
INTC NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH RRB
TRMB YES
STEP
ACOD 9752
TCPP NO
TARG
CLEN 1
BILN NO
OABS
INST
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096

IENB 5
TFD 0
VSS 0


PAGE 002

VGD 6
DRNG NO
CDR NO
VRAT NO
MUS NO
RACD NO
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
TDET NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO

Trunk:
DES CISCO
TN 056 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 6
RTMB 88 1
B-CHANNEL SIGNALING
TGAR 0
AST NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
AACR NO
This will allow you pass CLID from PBX to Cisco.
We are doing the opposite going from Cisco to CallPilot and even turning on the MWI on the Cisco phones from CallPilot.

Dwayne

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top