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

F9600 and Cisco Unity 5

Status
Not open for further replies.

JOY777

IS-IT--Management
Oct 30, 2006
4
Does anyone know what requirement(s)to get Fujitsu F9600 to work with Cisco Unity 5?
 
In this example several number ranges are routed from the PSTN to the Fujitsu F9600 to the Cisco Call Manager. At this site the F9600 supports 10,000 DID numbers and 17 Fujitsu Integrated Private Network (FIPN) sites and approximately 5000 users.
It supports Name and Number delivery between the two systems.
Incoming PSTN calls tandem through the F9600 to the CCM. CCM PSTN calls tandem back through the F9600 to the PSTN.

*** Note the Fujitsu PBX must have the following software to use the DMS100 protocol or the NI1/NI2 protocol to a Cisco Call Manager.
IPRCBS – ISDN Primary Rate Central Office Basic Service.

**** The following hardware is required on the Fujitsu F9600 system
1- BPTKCA, 1-B2DK2B plus the associated cables or 1-BPTKEA plus the associated cables.
See the Circuit Card guide for further details.

Build two trunk groups for the ISDN service, one is for B-channels and one is for the D-channel.
# TRUNK GROUP DATA LIST #

TGN TYP TID TNN SPC AKI COF TLT DGN RGN COS RSM FRL TRS HNT NAME
AKW AKR AKB RGT AOT GRD REL HKS AFT SHK RHK OPR DMF
MIN PRE MAK BRK DGT PST PBO PBF COP PGT MID
PAC MBC STG DT IAS DTS ABS DTK OOC NOC PTF TCS TCR TDT VCM OGF
CRC
NSF NSFFG PRMFF PRMFV CDNFG TON NPI
(Cisco TIE trunk B channels trunk group)
500 5 38 0 5 0 0 3 0 1 1 5 7 0 1 'VOIP'
0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0
28 0 0 0 0 0 0 0 1 21 0 0 0 0 0

0 0 0 0 0 0 0
(Cisco TIE trunk D channels trunk group)
501 5 37 0 4 0 0 0 1 1 1 1 1 0 0 'VOIP'
0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0
28 0 0 0 0 0 0 0 0 0 0 0 0 0 0

0 0 0 0 0 0 0

=>DIS ISINF,500


(PSTN is connected to the Fujitsu F9600, the Cisco CM is behind the Fujitsu. The Fujitsu RX the clocks from PSTN LD circuits and TX this clock to the Cisco CM)
*** Note if the Cisco is in front of the Fujitsu, the DMS100 protocol causes ISDN Information Element errors to the Cisco, therefore use the NI2 protocol instead, this disables Name & Number to/from the Fujitsu. The error is caused by a status message sent from the Fujitsu that the Cisco does not expect and causes calls to drop)
One other note, the names on the CCM must be all upper case to display properly on the F9600, this may be a character set problem that I have not gotten through yet.

# ISDN TRUNK INFORMATION LIST #

# ONE-INTERFACE #

< D-CHANNEL >

TNN TGN EN MS PRTCL

0 501 06081800 1 DMS100
(MS=1 Fujitsu is the master of the connection to Cisco, this site uses two ISDN PRI trunks)

< B-CHANNEL >

TNN TGN EN QDID FNA SUBDID DID UNA RSS RSASG TYP NSF

0 500 06081802 - - - - - - - MUL 0
0 500 06081803 - - - - - - - MUL 0
0 500 06081804 - - - - - - - MUL 0
0 500 06081805 - - - - - - - MUL 0
0 500 06081806 - - - - - - - MUL 0
0 500 06081807 - - - - - - - MUL 0
0 500 06081808 - - - - - - - MUL 0
0 500 06081809 - - - - - - - MUL 0
0 500 06081810 - - - - - - - MUL 0
0 500 06081811 - - - - - - - MUL 0
0 500 06081812 - - - - - - - MUL 0
0 500 06081813 - - - - - - - MUL 0
0 500 06081814 - - - - - - - MUL 0
0 500 06081815 - - - - - - - MUL 0
0 500 06081816 - - - - - - - MUL 0
0 500 06081817 - - - - - - - MUL 0
0 500 06081818 - - - - - - - MUL 0
0 500 06081819 - - - - - - - MUL 0
0 500 06081820 - - - - - - - MUL 0
0 500 06081821 - - - - - - - MUL 0
0 500 06081822 - - - - - - - MUL 0
0 500 06081823 - - - - - - - MUL 0
0 500 06081824 - - - - - - - MUL 0

< CBC GROUP TGN >

PILOT MTGN - NSF MTGN - NSF MTGN - NSF MTGN - NSF

NONE

# ONE-INTERFACE #

< D-CHANNEL >

TNN TGN EN MS PRTCL

0 501 06161600 1 DMS100

< B-CHANNEL >

TNN TGN EN QDID FNA SUBDID DID UNA RSS RSASG TYP NSF

0 500 06161602 - - - - - - - MUL 0
0 500 06161603 - - - - - - - MUL 0
0 500 06161604 - - - - - - - MUL 0
0 500 06161605 - - - - - - - MUL 0
0 500 06161606 - - - - - - - MUL 0
0 500 06161607 - - - - - - - MUL 0
0 500 06161608 - - - - - - - MUL 0
0 500 06161609 - - - - - - - MUL 0
0 500 06161610 - - - - - - - MUL 0
0 500 06161611 - - - - - - - MUL 0
0 500 06161612 - - - - - - - MUL 0
0 500 06161613 - - - - - - - MUL 0
0 500 06161614 - - - - - - - MUL 0
0 500 06161615 - - - - - - - MUL 0
0 500 06161616 - - - - - - - MUL 0
0 500 06161617 - - - - - - - MUL 0
0 500 06161618 - - - - - - - MUL 0
0 500 06161619 - - - - - - - MUL 0
0 500 06161620 - - - - - - - MUL 0
0 500 06161621 - - - - - - - MUL 0
0 500 06161622 - - - - - - - MUL 0
0 500 06161623 - - - - - - - MUL 0
0 500 06161624 - - - - - - - MUL 0

< CBC GROUP TGN >

PILOT MTGN - NSF MTGN - NSF MTGN - NSF MTGN - NSF

NONE

=>DIS SVP,2,67 (This service parameter will cause the F9600 to pass the AAR access code to the next node)
# SERVICE LIST #
TYPE = 2 ( SVSDT )
ID-----DATA
67 1


=>DIS NP,,,308
(Example of a number that belongs to the Cisco, all Fujitsu numbering/dialing plans are displayed)
****Note this access code can also be created as a TIE trunk access code (FNO 512~767).
Remember to add the FNO to the Class of Service assignments).
This implementation uses AAR access codes. By use of AAR, an ARS route is used to send the calling party name.

# NUMBERING PLAN LIST #

TNN= 0

TTID= 0 (General dial plan)

DIGIT EDL FNO TGN TGX AJC RDD DOC TTN DN SVN

308 5 304 0 3 0

TTID= 1 (Hook flash dial plan)

DIGIT EDL FNO TGN TGX AJC RDD DOC TTN DN SVN

308 5 304 0 3 0

TTID= 4 (Attendant console dial plan)

DIGIT EDL FNO TGN TGX AJC RDD DOC TTN DN SVN

308 5 304 0 3 0

TTID= 7 (TIE trunk dial plan)

DIGIT EDL FNO TGN TGX AJC RDD DOC TTN DN SVN

308 5 304 0 3 0

TTID= 8 (CO trunk dial plan)

DIGIT EDL FNO TGN TGX AJC RDD DOC TTN DN SVN

308 5 304 0 3 0


=>DIS AARLC,,308
(Automatic Alternate Route location code table for 308XX)

# AAR LOCATION CODE LIST #

TNN CODE XLC ARSTB EDL CODE XLC ARSTB EDL CODE XLC ARSTB EDL

0 308 500 5



=>DIS ARSR,500
(Automatic Route Selection for access code 308XX)

# ARS ROUTE TABLE LIST #

ARSTB TNN POS TGN FRL PTNNO T0 T1 T2 T3 T4 T5 T6 T7 LARF CMPF
(NARSTB) CDNFG TON NPI NAMF

500 0 1 500 0 0 * * * * * * * * 0 0
0 0 0 1 (NAMF used to send the name on this route, and is why AAR is used.)


=>DIS SVP,2,180 (Service parameters that effect Name & Number on tandem calls)

# SERVICE LIST #

TYPE = 2 ( SVSDT )

ID-----DATA ID-----DATA ID-----DATA ID-----DATA ID-----DATA

180 1 (Enable DMS100 Name display)

(Other service parameters in Group 2)

217 Calling party number to PRI-CO when 00:* Station calling line ID
TLTYP is TIE 01: Station DN (ISSLC + DN)
218 Calling party number when connecting 00:* Not provided
from PRI-TIE or PRI-CO to PRI-CO 01: Provided
222 Waiting trunk information display for call 00:* ‘OUTSIDE CALL’
waiting 01: Trunk information or calling
party information
(SVP 2,217= 0 to use the stations CLIST assignment SVP,2,218= 1 to pass through the CLID on a tandem call)
(SVP,2,222=1 to send CLID during call waiting.)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top