I have been seeing instances where the dialer throws a call to agent but the agent hears nothing. Further investigating I found the recording in such cases shows me the end portion of the fast busy message. Most of these dead air numbers are fast busy. It looks like for some reason there a delay induced. Any idea how to rectify this issue and allow the fast busy recording to reach agents in a timely manner.
Thanks,
I am using...
TA 908e 2nd Gen
Firmware : A4.08.00.E
Mcdeeiis,
Thanks for posting! There are a couple of common sources of delay that can be eliminated on the Adtran unit. For FXS applications, make sure you have a dial plan entry that matches the number pattern being dialed. Below is an example.
voice dial-plan 10 long-distance NXX-NXX-XXXX
For PRI applications, a common source of delay is waiting for caller ID name, though it should be turned off by default in the version of firmware you are running. Below is the command to turn off waiting for caller ID name.
interface pri 1
calling-party name-facility-timeout 0
If neither of these two settings seem to be the issue, we will need to check the debug output of test calls or possibly get a packet capture. If this is a SIP to FXS application, then we would need to see the following debug output in order to check for sources of delay.
debug sip stack message
debug sip cldu
debug voice verbose
debug interface fxs
If this is a SIP to PRI application, we would need to see the following in order to check for delay.
debug sip stack message
debug sip cldu
debug voice verbose
debug isdn L2-formatted
It would also be helpful if we had a copy of your configuration. However, please make sure any configuration or debug output does not contain sensitive information like IP addresses, phone numbers, etc.
Thanks!
David
Mcdeeiis,
Thanks for posting! There are a couple of common sources of delay that can be eliminated on the Adtran unit. For FXS applications, make sure you have a dial plan entry that matches the number pattern being dialed. Below is an example.
voice dial-plan 10 long-distance NXX-NXX-XXXX
For PRI applications, a common source of delay is waiting for caller ID name, though it should be turned off by default in the version of firmware you are running. Below is the command to turn off waiting for caller ID name.
interface pri 1
calling-party name-facility-timeout 0
If neither of these two settings seem to be the issue, we will need to check the debug output of test calls or possibly get a packet capture. If this is a SIP to FXS application, then we would need to see the following debug output in order to check for sources of delay.
debug sip stack message
debug sip cldu
debug voice verbose
debug interface fxs
If this is a SIP to PRI application, we would need to see the following in order to check for delay.
debug sip stack message
debug sip cldu
debug voice verbose
debug isdn L2-formatted
It would also be helpful if we had a copy of your configuration. However, please make sure any configuration or debug output does not contain sensitive information like IP addresses, phone numbers, etc.
Thanks!
David
Mcdeeiis,
I went ahead and flagged this post as "Assumed Answered". If the response on this thread assisted you, please mark it as Correct or Helpful as the case may be with the applicable buttons. This will make it visible and help other members of the community find solutions more easily. If you still need assistance, I would be more than happy to continue working with you on this - just let me know in a reply.
Thanks!
David