IP Office 3.2 - to - CM 3.1 for Conf Bridge. T-1 Trouble. 1

[Wolfcub1]

Hi jamcb80,
I am trying to connect my IP Office (3.2) to a CM 3.1 for the same conferenceing feature. But I can't get the t-1 pipe up.

We are only using one T-1 (and we are trying ISDN-PRI) but can change that to T-1.

What are you configs for the t-1 on each side????

Are you using a crossover T-1 cable????


We were using H.323 but without expanding the IP Office's VCM card I have a limit of 6 VoIP channels.

 

[sjforcum]

Yes it's a T-1 cross.

It's a tie line between the two boxes.

The extensions are added to your Uniform Dial Plan / AAR ANA tables and the "meet me" programming is done on the IP Office...

SJF

 

[Wolfcub1]

The meet me part is all working via H.323... the T-1 won't connect. I think we have bad config on the T-1s.

That is what I need help with.

Thanks,
J

 

[lopes1211]

If you are setting it up PRI, use a crossover cable and set the connect type on the Definity ds1 form to "line-side" instead of network.

-CL

 

[Wolfcub1]

I am using a T-1 crossover cable.
Here is my CM side:

DS1 CIRCUIT PACK

Location: 01B11 Name: IP Office Brdge
Bit Rate: 1.544 Line Coding: b8zs
Line Compensation: 1 Framing Mode: esf
Signaling Mode: isdn-pri
Connect: pbx Interface: peer-master
TN-C7 Long Timers? n Peer Protocol: Q-SIG
Interworking Message: PROGress Side: a
Interface Companding: mulaw CRC? n
Idle Code: 11111111
DCP/Analog Bearer Capability: 3.1kHz

T303 Timer(sec): 4


Slip Detection? n Near-end CSU Type: other

ESF DATA LINK OPTIONS

Network Management Protocol: tabs
Send ANSI-T1.403 One-Second Performance Reports? n
Far-end CSU Address: b


Here is my IP Office side:

PRI
5ESS AT&T
23->1

Network clock ESF
CRC 'Y' B8ZS
CPE


the channels are both ways, any service, none, and in service


Any thoughts on where there is a missmatch.


Jeff