07-15-2004 04:17 PM - edited 03-15-2019 02:57 AM
I'm trying to connection a 3745 and a Definity G3SI via a PRI connection. 3745 has a VWIC-2MFT-T1 installed. Definity has a DS1 circuit pack (TN767D?) Both sides are set to B8ZS/ESF. Using a straight through T1 cable using pairs 1/2 and 4/5. When connected there is no carrier detected on either side and the circuit never comes up. I've done this with another G3SI with a straight-through cable and it worked like a charm. I don't have the DS1 circuit pack model number to compare though, so they may be different.
Any suggestions? I've already read the interoperability white papers and they are of no help. I think it may be as simple as wrong cable but I'm wondering what other people are using.
07-15-2004 08:30 PM
I think you're using the wrong cable. You need a T1 "crossover" cable, not a straight-through. Construct a cable with pins 1 and 4 swapped, and pins 2 and 5 swapped. This swaps transmit and receive on one end, like you would do for an Ethernet crossover. This should bring the link up for you.
This integration should work for you just fine. If you can, use QSIG signaling on your PRI, as the Definity should support passing names and mid-call name and number updates in both directions.
07-16-2004 08:30 AM
Well, the PRI is up but I'm unable to pass calls either way.
Looking at my other integration, on the trunk configuration the service-type is tandem. On this it is set to public-ntwrk. Would that cause the rejection of calls?
07-16-2004 09:02 AM
Check out this URL, which shows how to do the Definity-side programming for a G3R. It's not the very same switch you have, but I think the config screens look much the same.
Use 'debug isdn q931' on the IOS router to troubleshoot calling back and forth. If you're getting 'Unallocated/unassigned number' rejections, you have a dial plan issue somewhere. There's lots of other possibilities that are too exhaustive to go through here.
I'm by no means a Definity expert. We usually have a contractor with expertise in whatever PBX we're integrating with handle that side. However, I think when you're using public-ntwrk, it's going to expect to be the User side of the PRI, whereas tandem means it wants to be the Network side of the PRI. You need to make sure the IOS and Definity are configured as opposites. Use network-side signaling on the IOS gateway if the Definity wants to be the User side.
07-16-2004 09:25 PM
can you post your definity config and router config and I should be able to help you out. on the pbx please do a display ds1 xxxx ( where x is hte board number) display trunk y ( where y is the trunk group) and a display isdn signaling z ( where z is the isdn signaling group. Also please send the router config. please make sure to get a snap shot of all pages on each display some displays have several pages.
hope to here from you.
scott
07-23-2004 03:33 PM
I've attached a text file with all the configs. I'm still unable to send calls between the two. I've configured the Definity according to the following white paper:
The only difference being that I am using MGCP instead of H323.
Any help or pointers would be great.
I don't have maintenance level permissions on this Definity so I can't do anything that involves busying out a signal group.
Thanks
07-23-2004 04:16 PM
Well, I guess this shows the D-Channel isn't coming up. The PRI in question is 4/1
VG-I-PREBLE#sh isdn stat
Global ISDN Switchtype = primary-ni
%Q.931 is backhauled to CCM-MANAGER on DSL 0. Layer 3 output may not apply
ISDN Serial4/0:23 interface
dsl 0, interface ISDN Switchtype = primary-ni
L2 Protocol = Q.921 L3 Protocol(s) = CCM-MANAGER
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0x807FFFFF
Number of L2 Discards = 0, L2 Session ID = 29
%Q.931 is backhauled to CCM-MANAGER on DSL 1. Layer 3 output may not apply
ISDN Serial4/1:23 interface
dsl 1, interface ISDN Switchtype = primary-ni
L2 Protocol = Q.921 L3 Protocol(s) = CCM-MANAGER
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 1 CCBs = 0
The Free Channel Mask: 0x807FFFFF
Number of L2 Discards = 0, L2 Session ID = 112
Total Allocated ISDN CCBs = 0
VG-I-PREBLE#
07-20-2004 06:46 AM
Its a good theory, but you may be incorrect. This G3 is set to public-network and network side. ;-) I figured all would be okay if I just set my side to user. But it didn't work.
Thanks everyone for the feedback. I'm not going to get a chance to tackle this until Friday evening so I won't be able to tell you if you suggestions worked. But thanks in advance.
07-15-2004 08:32 PM
Hello,
I will give you some simple suggestions in the hopes
that maybe you overlooked some minor detail.
First let me tell you that I have used straigt through cables when using the CSU that connects to the back of the circuit pack. But have used cross over cables on other external type csu/dsu.
I would try putting a Hardware loopback on either side to see if the T1 comes up.
No carrier on either side almost always points to cableing problems. Or bad CSU's
Also what are the LED's in front of the Circuit pack showing.
If you put a loopback on it does it change. If so which leds are green and which of the are red.
One other important setting is clocking, check to see that one is Master the other slave. Or in the router check to see if clock source is line or internal.
Hope this helps
Pablo Duarte
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide