Definity talkpaths

[hokey817]

I am having a few problems with my definity G3siV11. When a call is made it hangs there for sometimes as long as a minute until it finally dials. I have heard it is because the Definity only has 256 Talkpaths. Is there a way around this or does anyone know if talkpaths can be purchased for the definity. Thanks for anyone's input.

 

[adminman3]

Is it really hanging that long before it DIALS, or before you hear the ringing? Curious as to whether your trunk group is provisioned properly with your carrier. There have been outbound trunks mistakenly set up as Pulse rather than tone. This adds significant processing time, but I've not seen it take more than 7-10 seconds. Typical call setup ranges between .5 and 3 seconds.

For whatever this is worth.

 

[hokey817]

Thank you for your response. Yes I have waited about a minute for it to start ringing, but it is generally in the range of 10 to 20 seconds. I have already doubled check our carrier and also have double checked our trunk group and everything appears to be set up correctly. The only time this happens is on really busy traffic days.

 

[mikeydidit]

I have seen this before and anther post was done here not too long ago with the same problems. It was something that was done in the dialplan and the switch was waiting on another digit before placing the calls. I do not remember what the solution was but you may can do a search here and find it.

Mike Jones
LSUHSC

 

[jfh9219]

If mikeydidit is thinking what I am thinking, you can check to see if is the interdigit timeout by ending the number you are dialing with the #. This tells the switch that there are no more digits to wait for. There are a number of locations that interdigit timeout values can be set. The effect of the interdigit timeout can be affected by choices made for ARS analysis.

Try terminating the dialed digits with the # first.

 

[hokey817]

Ill check into both of those, but would this be a constant problem or just random problem as it is now?

 

[IPSI]

You may want to check and see if your outbound trunk group is setup with a queue (first page of the trunk group form).

The reason that I mention this is because you stated that this only happens on busy days. If you have a queue setup for a trunk group, and all members of the trunk group are in use, your call will just sit there and wait for the next channel to open up before the call is completed and this could be just a few seconds, or much longer if there are multiple calls in the queue.

I hope this helps!

IPSI

 

[hokey817]

Thanks everyone for their input. I have checked the trunk and have isolated the problem to one port. Right now this port takes some time to initiate the call and I have it busied out so no one will complain about this problem, however what could be the cause of this and how can this be corrected. Could it be a bad port on the card? Is there a way to test this? Thank you again.

 

[mikeydidit]

If you have an extra trunk port that is not being used you can wire it up on it and see if the problem remains. If so then you then your service provider will have to send out a tech to fix cable pairs ect. You can also swap trunk ports on a card for testing. Use a verify button on your phone, enter the TAC and then enter the trunk number to place calls out over this to see if the problem follows the port. (If this is OGO)

Mike Jones
LSUHSC

 

[wmharris]

If you have a large number of calls and other services using the TDM buss the system may be overloaded. The only way to stop this is to add another port network (i.e. cabinet). The TDM buss has a maximum limit of just 483 time slots available per port network.