dropped calls on PRI

[phoneguy99]

I have been reading past info from you guys and I can't find my answer. Does 3.156 have a problem with dropping calls randomly with a PRI? I have two sites that are having this problem and I have had the service provider test the PRIs with no problem. Can you help me?

 

[NuggiFirst]

We have lots of 3.1(56) systems with PRI-lines, but none with this problem.

Try running Monitor with only ISDN layer3 tx/rx enabled, and see if either the CO or the IPO initiates the Disconnect procedure.

 

[jconrad0305]

you may want to make sure that in the processor you have all of the pins in the slot for the pri card. missing one or 2 will cause goofy problems. also look under the monitor app. any call dropped with have a disconnect code associated with it. this may help you find out what is going one.

 

[SuperJenks]

Yes, there is a known problem with this. Is the system a 406 etc? There is a also a paging issue that is related to dropped calls on a pri. I have 2 sites experiencing this problem. Hopefully it will be resolved in the next GA but wouldnt hold your breath. Its hard enough just getting avaya to admit there truly is a problem to begin with let alone expect it to be fixed in the next GA>

 

[mforrence]

SuperJenks - can you describe the problem in greater detail? I have a site with 406v2 and some odd PRI/paging troubles that I haven't been able to pin down. Thanks
Mike

 

[SuperJenks]

This seems to happen on systems that have 30 or more sets. On 3.1.56, if you make a page over the phones and change your mind and hang up before all the phones become active for the page, the phones will go on and off hook repeatedly until you unplug the sets or reboot the system. I think this is when the dropped calls occur durring this state of mayhem. This is a big problem for our customers. Waiting for a fix from avaya.

 

[phoneguy99]

Thankyou for your info. I am having the exact same problem as SuperJenks with paging and PRI. It is nice to see that Avaya does admit there is a problem now.

 

[superikey]

Does anyone know if this was fixed in 3.1.65? We are deplying a 110 user Site in the next month and want to avoid having this issue.

 

[SuperJenks]

Should be resolved in 3.1.65