Problem with ISDN QSIG IP office and Siemens HiPath

[johnromani]

Hi all,
I have a little doubt with the configuration using IP Office connected with Siemens HiPath4000 over ISDN QSIG.

The calls goes and went perfectly during all the day, but sometimes we cannot receive or make call over the trunk.

My topology is: Tel IP ---{IP Office}---QSIG---{HiPath4000)---Analog Tel

This is the ISDN messages that I got under the tels cannot make or receive calls. Just for example, the 5959 is a IP Tel 1608 (from IP Office) and the 0569 is the Siemens Tel:

4788870mS ISDNL1Rx: v=9 peb=9
0000 02 01 7c b0 08 02 00 06 05 04 03 80 90 a3 18 03 ..|.............
0010 a9 83 9e 6c 06 00 83 30 35 36 39 70 05 80 35 39 ...l...0569p..59
0020 35 39 7d 02 91 81 59}...
4788870mS ISDNL2Rx: v=9 peb=9
0000 02 01 7c b0 08 02 00 06 05 04 03 80 90 a3 18 03 ..|.............
0010 a9 83 9e 6c 06 00 83 30 35 36 39 70 05 80 35 39 ...l...0569p..59
0020 35 39 7d 02 91 81 59}...
4788870mS ISDNL3Rx: v=9 peb=9
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0006(Remote)
Message Type = Setup
InformationElement = BearerCapability
0000 04 03 80 90 a3 .....
InformationElement = CHI
0000 18 03 a9 83 9e .....
InformationElement = CallingPartyNumber
0000 6c 06 00 83 30 35 36 39 l...0569
InformationElement = CalledPartyNumber
0000 70 05 80 35 39 35 39 p..5959
InformationElement = HigherLayerCompat
0000 7d 02 91 81 }...
4788871mS ISDNL3Tx: v=9 peb=9
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0006(Local)
Message Type = ReleaseComplete
InformationElement = CAUSE
0000 08 02 80 91 ....
4788871mS ISDNL2Tx: v=9 peb=9
0000 00 01 b0 7e 08 02 80 06 5a 08 02 80 91 ...~....Z....
4788872mS ISDNL1Tx: v=9 peb=9
0000 00 01 b0 7e 08 02 80 06 5a 08 02 80 91 ...~....Z....
4788969mS ISDNL1Rx: v=9 peb=9
0000 00 01 01 b2 ....
4788969mS ISDNL2Rx: v=9 peb=9
0000 00 01 01 b2 ....
4841335mS ISDNL3Tx: v=9 peb=9
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0045(Remote)
Message Type = Disconnect
InformationElement = CAUSE
0000 08 02 80 a6 ....
4841335mS ISDNL2Tx: v=9 peb=9
0000 00 01 ca 94 08 02 00 45 45 08 02 80 a6 .......EE....
4841336mS ISDNL1Tx: v=9 peb=9
0000 00 01 ca 94 08 02 00 45 45 08 02 80 a6 .......EE....

I can see that the problem could be this line:
InformationElement = CHI
0000 18 03 a9 83 9e
But I don't know what can I do...

Best Regards,

Cesar Romani
Avaya ACSS | APSS (SME/Data)| ACIS (Data)
Comptia Convergence +

 

[Okkie26]

How did you setup the ISDN port on the Siemens PBX?

I have setup Hipath 3000 to the IP Office 406 using the 'Fax Server' option on the Siemens trunk.
So the Siemens is setuo as S0 using Qsig.

Works like a charm..

 

[Bas1234]

Do a search here i've put the colpleet manual on here somewhere.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[johnromani]

Just in case, the trunk configured now is a tie line using PRI QSIG B, not the h450... I think the configuration is a little bit different, right?

Cesar Romani
Avaya ACSS | APSS (SME/Data)| ACIS (Data)
Comptia Convergence +

 

[johnromani]

Updating the topology:

[IP office 1]
[IP office 2] -- h450 -- [IP Office Main ]---QsigB---[Siemens HiPath]-----{bunch of analog phones}
[IP office 3] {IP Phones}

On the IP office Main we have:

60 Voice Networking Channels
46 PRI Channels
1 Dual PRI Card
1 Single PRI

TheTrunk with subtype QSIGB is configured with 30 channels (Channels, Voice and Data)

There are other trunks configured as H450 (around 6 or five line IDs), major of them configured with 3 channels only and 2 others main lines configured with 15 channels each them.

Cesar Romani
Avaya ACSS | APSS (SME/Data)| ACIS (Data)
Comptia Convergence +

 

[johnromani]

Update:

The siemens side is configured with ETSI.

The system works fine until suddenly the avaya phone cannot call the siemens and the siemens phone cannot call avaya's phone.



Cesar Romani
Avaya ACSS | APSS (SME/Data)| ACIS (Data)
Comptia Convergence +

 

[Bas1234]

Check these options.

http://tek-tips.com/viewthread.cfm?qid=1666997

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[johnromani]

Hello Bas1234,

We'll try to set the Siemens on ECMAV2 and check if it works. We can try to set ETSi on both sides, should works fine too, right?

The another thing that is driving me crazy: The licenses "IP500 Universal Pri (Additional Channel)" are displayed as: Available 46, And in use is "stucked" in 29 channels.

We have another PRI configured as E1R2 with 15 channels; Where is the 14 channels in use? This QSIG trunk is using these licenses? I cannot understand the realtime view....

The config is:

Line 9: QSIG B = 30 channels
Line 10: ETSI (30 channels out of service)
Line 13: E1R2 15 channels in service

Cesar Romani
Avaya ACSS | APSS (SME/Data)| ACIS (Data)
Comptia Convergence +

 

[johnromani]

Updating:

The problem was solved when changed the Siemens side to ECMAV2.

When the Siemens side was ETSI, it works, but the call flow was increasing ever and ever until the system has stopped to work.

Thanks all!

Cesar Romani
Avaya ACSS | APSS (SME/Data)| ACIS (Data)
Comptia Convergence +