Odd problem dialing out. 1

[mrchris]

Ip Office SOE (4A-4T-8DS-16vc) 3.0.59....I have two users complaining that about half the time they dial out the calls either drop before they dial or they dial and the operator (phone company) recording comes on saying their call could not be completed as dialed. I have made about 50 test calls from each extension and cannot duplicate the issue, nor are the other 5 users having any problems.

These are basic analog lines, no caller id.......any thoughts?

 

[auEric]

Have you test all trunks are working and/or not restricted to local calls only? Do you have any ports in the outgoing group that are not connected?

 

[JeSTeROCK]

Had a similar problem on a SOE but also with calls dropping out. Changed hardware, same result

Erased and reprogrammed and all is good so far

 

[mrchris]

Well, blasted the config and reprogrammed as suggested, so far no complaints. Odd though, pretty basic config there wasnt much to it to get screwed up. Thanks

 

[bakeacake]

I normaly have people having problems with the dial delay count i.e. dialing to slow or stopping after 3 or 4 digets

HTH

 

[Ant007]

I was about to request some help with the same problem.
I have 40 ext system and randomly analogue users get the same problem as listed above.
We have collated a SMDR log and a Trace log and established that the unconnected call tries to use PRI line 5(which only comes up when the call will not connect).
I was considering replacing the analogue expansion, the ISDN card the shielded cat5 cable and changing the port that the expansion is plugged into on the back of the 406.
I have upgraded the software, still lots of problems.
Does anyone know what PRI Line 5 represents/means,
weather it is a hardware error, or weather I need just to rebuild the config(can it be that simple?).
Any help would save me a lot of heartache.

 

[CiCiNL]

I have had this simmilar problem when the IPO is setup with '0' for trunk access and using analogue phones with autodial option like Siemens DECT phones and faxes.

 

[knuckleweasel]

IF YOU HAVE 8 ANALOG PORTS ON YOUR SWITCH AND ARE ONLY USING 6 LINES YOU NEED TO MAKE PORTS 7 AND 8 OUT OF SERVICE OR WHEN YOU DIAL 9 FOR AN OUTSIDE DIAL TONE THE SWITCH WILL PICK UP PORTS 7 AND 8 WHICH DO NOT HAVE A DIAL TONE. THEN IT DROPS THE CALLS.

 

[intrigrant]

knucleweasel actually means that non-used trunks should have different incoming and outgoing line-IDs as the used trunks have.
This could very well be your problem.
Another problem can be the Dial Delay Timer and Dial Delay Count settings in System->Telephony as bakeacake suggested.
But of course it can be anything else also.
Using Sysmon would help if you know how to interpret the messages ( and there are a lot of them )

 

[Ant007]

If say the problem is the Dial Delay Timer and the Dial Delay Count - What do suggest thes settings should be set to.

 

[mrchris]

Hmmm still having some problems, actually seems to be two different issues, lengthened the dialdelay and that helped some in that the slow dialers arent getting issues quite as often. I ran sysmonitor and watched a few calls go through, a couple of calls still immediately dropped and the monitor showed one line that concerned me "trunk seize" ......

 

[Webnx]

Sounds like this is common. we are having the exact same problem, well both problems. the first one is people don't dial fast enough and it drops the call. that problem is a no brainer as the timeout is set to 4 seconds. now the real problem happens as random, but it happens alot. it seems related to certin numbers, you try to call them a few time and it just hangs up, test the number with a cell phone and it works fine. at this point we have a digital t1, for our outbound lines, so my guess is it has something to do with the t1, or the t1 provider. I will keep you guys posted as I test.

 

[JeSTeROCK]

In general you should set the dial delay counter to be one more than the length of your externsion ie. 3 digit ext numbers dial delay count of 4

Dial delay timeout of 1000ms

If this doesn't fix it i think its the config database. Did everyone default the system before they started programming ?

 

[jslewis]

I am having the exact same problem that Webnx is talking about, except it is on a pri instead of a T1.
My client has a 406v2 ver 3.0.40. There is a number that one user dials quite often, she will get a disconnect many times in a row, but a cell will go through. Then every once in a while the number will connect without a problem. Other users at the site have reported random disconnects.
Wondering if this is 3.0 feature?

 

[intrigrant]

I suppose you should switch from overlap to en bloc dialling on your trunks.
The advantage of en bloc dialling is that the user has some more time to complete the whole number but it will take some more time before the actual connection is made.

There are examples within this forum wich explains both versions.