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!

Nortel & Cisco playing nice except...

Status
Not open for further replies.

robust57

IS-IT--Management
Apr 14, 2005
65
US
Recently we setup a Cisco Unified Call Manager and this weekend we integrated it into our Nortel 61C.

Physical connectivity is:
We have 3 PRIs that connect directly into a Cisco 3925 router. From that 3925 we have QSIQ (3 PRIs) into the Nortel

All call scenarios that I can come up work except for one where hunting rules on the Nortel side come into play. That situation is when a Nortel user is on their primary line, key 0, (LHK is set to 1) and a second outside call comes in to the same DID as on key 0. What happens is that the line on key 1 will buzz briefly, like a half ring. Then the caller hear's "We're sorry all cirucuits are busy, please try your number again."

Its like the Nortel properly routes the call then takes it back.

I can get around this by programming a MCR but I don't want to reprogram 1000 phones from SCR/N to MCR/N.



Any ideas?
 
D-channel messages

DCH 6 UIPE_OMSG CC_SETUP_REQ REF 000001A9 CH 6 23 TOD 17:40:30 CK B5E7E209
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:8420 NUM PLAN: PRIVATE TON: ESN CDP
CALLED #:8051 NUM PLAN: PRIVATE TON: ESN CDP

DCH 6 UIPE_IMSG CC_PROCEED_IND REF 000001A9 CH 6 23 TOD 17:40:32 CK B5E7E343

DCH 6 UIPE_IMSG CC_ALERT_IND REF 000001A9 CH 6 23 TOD 17:40:32 CK B5E7E350
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 6 UIPE_IMSG CC_SETUP_CONF REF 000001A9 CH 6 23 TOD 17:40:34 CK B5E7F90D

DCH 5 UIPE_IMSG CC_SETUP_IND REF 00005981 CH 5 23 TOD 17:40:40 CK B5E8252C
CALLED #:8420 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:3036686021 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_MORE_INFO_REQ REF 0000D981 CH 5 23 TOD 17:40:40 CK B5E82537

DCH 5 UIPE_OMSG CC_PROCEED_REQ REF 0000D981 CH 5 23 TOD 17:40:40 CK B5E8255A

DCH 5 UIPE_OMSG CC_FAC_REQ REF 0000D981 CH 0 TOD 17:40:40 CK B5E82567

DCH 5 UIPE_OMSG CC_ALERT_REQ REF 0000D981 CH 5 23 TOD 17:40:40 CK B5E8257C
PROGRESS: TERMINATING END IS NOT ISDN

DCH 5 UIPE_IMSG CC_RELEASE_IND REF 00005981 CH 5 23 TOD 17:40:40 CK B5E8260C
CAUSE: #101 - MSG NOT COMPAT WITH CALL


DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 0000D981 CH 5 23 TOD 17:40:40 CK B5E82616

DCH 6 UIPE_OMSG CC_DISC_REQ REF 000001A9 CH 6 23 TOD 17:40:54 CK B5E8930A
CAUSE: #16 - NORMAL CALL CLEARING

DCH 6 UIPE_IMSG CC_RELEASE_IND REF 000001A9 CH 6 23 TOD 17:40:54 CK B5E89387

DCH 6 UIPE_OMSG CC_RELEASE_RESP REF 000001A9 CH 6 23 TOD 17:40:54 CK B5E89393
 
Issue was on the Cisco side, wasn't setup properly for QSIG. Vendor set all ports to NI2 on Cisco router.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top