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!

Avaya CM/INDeX Qsig problem 1

Status
Not open for further replies.

bsmo

Technical User
Aug 11, 2005
139
BE
Hello,

Has anyone succesfully setup a connection between an Index and an S8300/G700 ? I'm not getting the link into service. Qsig from Index to Siemens is working and Qsig from Siemens to CM is also working.

Any special settings that need to be done ?

Regards,
Bram
 
First we should know on which step you have a problem: wiring,
line coding or signaling, or dialing?

Did you test board?
status signaling-group and trunk-group?
 
Dimas,

When I plug in the cable the alarm clears so I think the cable should be ok.

Here are my settings:

DS1 CIRCUIT PACK

Location: 001V4 Name: Qsig To INDeX
Bit Rate: 2.048 Line Coding: hdb3

Signaling Mode: isdn-pri
Connect: pbx Interface: peer-slave
TN-C7 Long Timers? n Peer Protocol: Q-SIG
Interworking Message: PROGress Side: b
Interface Companding: alaw CRC? y
Idle Code: 01010100 Channel Numbering: timeslot
DCP/Analog Bearer Capability: 3.1kHz

T303 Timer(sec): 4


Slip Detection? n Near-end CSU Type: other

Echo Cancellation? n

SIGNALING GROUP

Group Number: 1 Group Type: isdn-pri
Associated Signaling? y Max number of NCA TSC: 0
Primary D-Channel: 001V416 Max number of CA TSC: 0
Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 1
Supplementary Service Protocol: b Network Call Transfer? n

TRUNK GROUP

Group Number: 1 Group Type: isdn CDR Reports: y
Group Name: Qsig To INDeX COR: 1 TN: 1 TAC: 9001
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 99 Night Service:
Queue Length: 100
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: cyclical QSIG Value-Added? n
Digital Loss Group: 13
Incoming Calling Number - Delete: Insert: Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? y
Answer Supervision Timeout: 0

STATUS SIGNALING GROUP

Group ID: 1 Active NCA-TSC Count: 0
Group Type: isdn-pri Active CA-TSC Count: 0
Signaling Type: facility associated signaling
Group State: out-of-service


Primary D-Channel


Port: 001V416 Level 3 State: out-of-service


Secondary D-Channel


Port: Level 3 State: no-link


TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

001V4 MG-DS1 138 PASS
001V4 MG-DS1 139 PASS
001V4 MG-DS1 140 PASS
001V4 MG-DS1 141 FAIL
001V4 MG-DS1 142 PASS
001V4 MG-DS1 143 PASS
001V4 MG-DS1 144 FAIL 25
001V4 MG-DS1 145 PASS
001V4 MG-DS1 146 PASS
001V401 ISDN-TRK 0001/001 36 PASS
001V401 ISDN-TRK 0001/001 255 FAIL 8
001V401 ISDN-TRK 0001/001 256 ABORT 1116
001V401 ISDN-TRK 0001/001 257 ABORT 1116
001V402 ISDN-TRK 0001/002 36 PASS
001V402 ISDN-TRK 0001/002 255 FAIL 8
 
Are you sure that CRC is enabled on remote end?
 
dimas,

Yes, CRC is on at the Index side.
 
Did you check that InDex-Master, S8300-Slave, yes?
How your E1 channel is organized? Do you have a provider network between S8300 and Index? Some E1 network facilities need to have CRC settings too. If possible try to install loopback somewhere on the network in S8300 direction, all tests from 138 to 146 should be PASS (if loopback is setted and no cable faults).
 
Failing test 141 is a yellow alarm which means you are not framming. Are you sure the line coding is correct? The repair proceedure is as follows:

If the MM710 connects to a line-side terminating device (for example, a PRI terminal adapter), do the following:
1. Verify that the switch DS1 and the line-side terminating device are administered using the same signaling mode, framing mode, and line coding.
2. Investigate the maintenance status of the line-side terminating device. Refer to the ’Line-Side Terminating Device Operating Manual’ for information.
3. Check the physical connection of the MM710 interface Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures.
4. Replace the local MM710 interface Media Module and repeat the test.
5. Contact the vendor of the line-side terminating device to diagnose the equipment.

Failure of test 144 is slips and the code indicates the number of slips per test interval. If you repair your yellow alarm, this should go away, otherwise repiar proceedures are:

If the MM710 connects to a line-side terminating device (for example, a PRI terminal adapter), do the following:
1. Retry the command at 1-minute intervals for a maximum of 5 times.
2. Enter the list measurement ds1-log location command
to read the error seconds measurement.
3. Verify that the switch DS1 and the line-side terminating device are administered using the same signaling mode, framing mode, and line coding.
4. Investigate the maintenance status of the line-side terminating device. Refer to the ’Line-Side Terminating Device Operating Manual’ for information.
5. Check the physical connection of the MM710 interface Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures.
6. Replace the local MM710 interface Media Module and repeat the test.
7. Contact the vendor of the line-side terminating device to diagnose the equipment.

I agree with dimas that troubleshooting should start with a loop-back to both systems to eliminate cable and/or hardware faults.
 
Everyone thanks for the help but I solved it. It seems the cable length was just on the edge. I took another circuit and now everything is functioning.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top