Meridian Option 81c INI issue due to MW light issue with Unity.

[Meridianman5]

I had an issue yesterday with our PBX INI'ing and our level 2 support people are informing me that the Message Waiting indication was "stuck Ping ponging" between the Unity and the pbx. I was also told that we need to upload a "Ping Pong patch" to each pbx we have to alleviate this issue. Has anyone heard of this issue before? Is there any other issues we need to look at to find out why/how we can circumvent any more issues going forward? The INI disabled the DCH on our DID route and we were without DID to our site for a couple hours. Thanks in advance!


"If it doesn't kill you, it will only make you want it to!

 

[yyrkroon]

Post the patch number that your support people told you that you needed.

 

[Meridianman5]

I am waiting for their response, any ideas?

 

[yyrkroon]

No idea, not without further info...like the actual INI code anything from the rdlog or history file prior to the INI and after the INI

 

[Meridianman5]

just an update, the "ping pong" patch was uploaded successfully, stay tuned for updates.

 

[jneiberger]

Out of curiosity, how was Unity connected to the PBX? Was it directly connected or do you have it integrated over QSIG or something else?

 

[Meridianman5]

PRI point to point via QSIG. I was not told of the patch "number" just that it was the "ping pong" patch being aa known issue w/ Meridian to Unity migration.

 

[jneiberger]

What software are you running on the 81c?

 

[Meridianman5]

Succession 3.0

 

[StanleySteamer]

Nortel issues Deplist Paks (Dependency List Packages) that include all the patches that they recommend should be applied to all switches.
A new deplist for 3.00 was released yesterday. I think the previous deplist for 3.00 was back in June 2005.
You may want to ask your vendor about keeping your switches updated with the latest deplists as they come out. Maybe they already do. The ping-pong patch may not have been included on the last deplist.

 

[Meridianman5]

Thanks for the info, ironically the same thing just happened this morning at our other location..the call registers were an issue after the ping pong effect maxed out the dchannel resources according to our vendor. I shoulda went to law school like my mother told me, gotta love technology!

 

[dlesap]

Hello

We had the same problem on 2 Opt61C CPP rls 3.0.
Init occurs continualy. Our lab solve the problem but don't know how. I will keep you all informed

 

[Meridianman5]

hey there dlesap, any idea on how the fix was found?

 

[dlesap]

Hello

These systems init continually cause of PSTN errors, it seems...not sure.
Anyway, Nortel ask to install patch 19982 and solve the problem.

Regards