Outgoing call problem on IP403

[IPONEWBIE1]

I have a customer with a IP403 and 3.1. They have 2 atm4 trunk cards. When they go to make a outgoing call sometimes it will not go through. This doesnt happen all of the time. It happens with all of the phones and not any phone in particular. They will get a busy signal (slow busy) or dead air. If they try 2-4 more times it will go through. It sound like the call is being trapped at the telco side. Our local telco is At-T/Bellsouth.

If anyone is wondering, I cant upgrade to 3.2 right now because they cant take their phones offline long enough to make the upgrade.

All of the analog settings are default and never been changed. Is there a setting that I can change like DTMF, GAINS, PULSE WIDTH, AWAIT DIAL TONE?

Any help in this is greatly appreciated.
Thanks

 

[ProviderReborn]

This sounds like some of the lines have gone down.
I would disconnect each trunk from the IP Office and ensure you have dial tone and can make a call.
WHats happening is the system is jumping throuhgh the OLG lines and possibly hitting a dead line/channel.

ACA - IP Office Implement
ACA - IP Telephony
CCENT - Cisco ICND1
CCNA - Working towards.

 

[IPONEWBIE1]

They had Bellsouth out there yesterday to check the lines. I am using 7 trunks, trunk 8 was set to 9999 incoming and 9999 outgoing so it doesnt try to get used. I can watch in system status and see all 7 lines being used for incoming (I am remote) so I know that each trunk is active.

 

[IPONEWBIE1]

I did a site visit and of course everything is working fine. All 7 lines are clear and I can make calls. It is happening totally randomly regardless of how many lines are in use. Is there any setting in the analog setting side that anyone has played with and had good luck?

 

[Telecomboy]

Are they actual POTS lines being delivered or is the service being delivered via a T1 that is then emulating POTS lines?

 

[IPONEWBIE1]

True POTS lines, they had a problem a few weeks ago with bad crosstalk problems and after going back and forth with bellsouth and myself and this routine that everyone knows all too well (Its not bellsouths problem you need to call your phone guy, Its not my problem you need to call bellsouth) Bellsouth finally admitted they had some bad lines and pulled a new 10 pair from their street demarc to the customers 66 block. Knowing this, I can pretty much rule out a wiring problem since it is all new and accept that there may be a problem with the PBX.

So to answer your question yes they are POTS and they are only about two weeks old.

Bellsouth was out there a few days ago and checked all connections and was able to make calls on every line. I can confirm that all lines are working because it shows in sys status.

 

[digital12188]

Since it happens randemly and to all the phones, is it possibly that all 7 lines are busy and when 8th caller tries to make call the ey get your above symptoms??

Try running monitor on system for a while and see if you can catch it>>

 

[IPONEWBIE1]

That is what I thought but it will happen with only 1 or 2 people on the phone and the third tries to make a call.

 

[tlpeter]

Also new stuff can be bad
They made a new cable from the street but what if that was not done well ?
Crosstalk sounds like a wet cable !


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[digital12188]

Have you checked all setting on the trunks? Make sure they are the same.. When you were on site did u use a butt set on lines and checked them yourself... telco always say everything is fine on our end... Check all x connects/ wiring from dmarc to PBX..

Use monotor and see if you can see anything..

 

[IPONEWBIE1]

What settings would you chose on sysmon so I dont have to sort through mounds of data???

 

[IPONEWBIE1]

One thing I notice is I keep getting a "ATM CHANNEL (any channel) SLOPPY TIMEOUT WAS 200ms

 

[IPONEWBIE1]

Anotherthing I notice is there is a LCR NOT MATCHED:2961 Does that mean anything?

 

[TourPro]

Try checking the "Long CLI Line" box in the line form.

ACA - Implement: IP Telephony
ACS - Implement: IP Office