Avaya Definity to Mitel MXe-III - QSIG issues.... 3

[pwsymonds]

Hi All,

Hoping for some help here...We have seemingly successfully set up a tie between the two systems. We made a call between the two systems (worked, both directions) and a call from external directly to a mitel extension (again both ways (so TO an external number from the mitel phone).

The issue we are having is one of intermittent nature (so far, i'm trying my best to replicate).

It seems whilst this intermittent issue is occurring, the tie goes into some sort of meltdown. Calls from the avaya to the mitel dont work..You can call the extension from the avaya phone, but you wont get any ringing dial tone HOWEVER the mitel handset will actually physically ring! You can then answer it but it wont carry or receive any voice/sound.

Calls from external are handled oddly as well. Very hard to describe but it seems if i were to initiate a call on my mobile to my mitel extension, and the guy behind me on another extension rings HIS OWN extension on his mobile and we both answer, it enters some kind of a conference mode.

The issue seems to remain for about 30 - 45 mintues and then the tie goes back to working again without issues.

Odd indeed. Any ideas? I'm trying my best to replicate so i know what triggers this issue but no luck so far.

Any kind of suggestions would be great!

Cheers
Pete

 

[danramirez]

Pete,

That happened to me last year with a 3300 and an Avaya IP Office. What I did to sort it out was to change who the master and slave were. At the beginning I had the mitel as Master but I was having that same issue you are reporting, at the end I set the Mitel as Slave and the Avaya as Master.

I didn't received much help from the Avaya Technician so I kind of had to do the programming on the Avaya side as well, which I have no experience whatsoever.

Here is What I did:

https://www.dropbox.com/s/j57epgb874kkgqo/Avaya IP Office and Mitel QSIG TEK-TIPS.pdf?dl=0

Cheers,

Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[pwsymonds]

Thanks for helping, seriously.

Ill get back to you with the results !

Pete

 

[danramirez]

Pete,

I forgot to mention that this was installed on the island of Curazao and the Avaya was equipped with a T1 card, apparently there are T1 cards and E1 cards but not T1/E1 as there are for the Mitel. So I had to use T1 format instead of E1 which I had preferred.

Good Luck, Cheers,

Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[pwsymonds]

Hi

UPDATE: i looked at all the settings and everything seems similar to yours (only using an E1 interface and a few other differences)...

However, it happened again so i logged on to the mitel interface and as soon as i "disabled" network synchronization as per your document notes ...the phones came back to life, where normally it would take an hour or so to fix itself! (not even a system reboot)

Lets see what happens over the course of next week and ill report back but it looks to be solved by disabling that option

Thanks Daniel....

Pete

 

[pwsymonds]

Try again....

The issue came back. I can only think this has something to do with slippage and clock synchronization. Not sure if i actually disabled network sync on the mitel or just got rid of the clock source fields to be honest...Daniel, any idea how you actually "disabled" the network sync function in the webUI on mitel?

I've asked mitel to take a look in the meantime and again ill update you...

 

[danramirez]

Under Trunks -> Digital you will find Network Synchronization form. Make sure you have no PLID for any of the clock sources.

This way your Qsig will be in Free Run and will not expect any clocking from anywhere.

I could do this as I had no other Digital Trunks to the PSTN, but if in your case you have another PRI to the PSTN I will not suggest you clear the network sources.

You did good by raising a ticket with the support guys.

cheers,

daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[Lundah]

If the only digital trunks you have on the Mitel is the QSIG link to the Avaya, I'd set the network synchronization form to clock off the QSIG link, especially if the Avaya is sourcing its own clocking off a circuit to a telco somewhere.

I've got a few QSIG's that were originally to a Definity and now connected to an Aura, and have had very few issues with them. The only other form that would really impact this is ISDN Protocol, which for mine are left default other than the protocol and variant fields being Q.SIG and ISO, respectively. Is the circuit connected via an embedded E1/T1 module, or is there an NSU?

 

[pwsymonds]

Update

I know the update is much delayed but after a lot of finger pointing from avaya i decided to spend a day working out the issue myself and i have worked out where its going wrong, i just need to find a fix for it now.

It seems when the call hits the 16th member of trunk 3, i get a denial event 1175 - ISDN channel unacceptable. Calls made onward form that moment increment in members to number 30, each call between members 17-30 does go through (so no further denial event) but NO VOICE or DIALTONE is carried. Once it goes back round to member 1 in the trunk, the calls start working again up until, you guessed it, member 16.

if anyone has any ideas let me know, otherwise ill let you know once i work it out. Hopefully with more help from both vendors now

 

[Billz66]

channel 16 is often used for the signalling channel on E1 links

are both sides configured with the same amount of trunks and same protocols

If I never did anything I'd never done before , I'd never do anything.....

and due to an endless stream of MiCollab , MiCC issues
Life would be simpler If only they tested products properly before releasing them .....

 

[pwsymonds]

Yea was just doing some research and found the same info

https://downloads.avaya.com/elmodocs2/s8700/cmain/MaintenanceChapter0668.html

Looks like that could be where the mismatch is. Our Avaya trunk does not skip any members as such, but the 16th member is assigned to port 01B1617 (skipping the port reserved for signalling, which is 01B1616). So it skips the port, if that makes sense?

The mitel also has 30 members but looks like its 16th member is also the 16th circuit? (Port?).

I'm not quite sure where to go from here so i might contact mitel and avaya with my findings, any ideas?

 

[pwsymonds]

Set sequential channel numbering to true (option under Trunks > Digital > ISDN > ISDN Protocol) and what do you know, issue resolved!

Thanks for all your input everyone, learned a lot more than i thought i would!

 

[Rixy]

Pwsmonds, nice one on resolving that. and thanks for posting the resolution.