| Summary: | ASTERISK-05163: Call jumps into Digital Receptionist and is then dropped | ||
| Reporter: | James Flesher (jflesher) | Labels: | |
| Date Opened: | 2005-09-27 14:47:21 | Date Closed: | 2011-06-07 14:10:01 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | During a conversation the digital receptionist will begin playing in which both parties can hear. After the menu has fully played and the digit response timeout period expires the call is dropped. This has been a problem for us for both manual configurations and installations of the AMP Portal. This has been a problem we have experienced for every version of Asterisk available in the last year as that is the length of time we have been utilizing this system. We have three Sipura 3000 devices for incoming and outgoing calls as well as configurations for FWD, VoicePulse and a direct IAX2 connection with another Asterisk phone system. We are running the latest version of the Sipura firmware. 3.1.5(GWb) on all three devices. | ||
| Comments: | By: James Flesher (jflesher) 2005-09-27 14:49:21 This problem is intermitent as it does not happen on a regular basis and we have not been able to reproduce. There are times in which we experience this problem multiple times a day or it may takes weeks to show it's ugly head again. By: Michael Jerris (mikej) 2005-09-27 15:49:47 I am not farmiliar with the term "digital receptionist" as being anything that is part of asterisk. What is actually happening, can you attach a full call trace of a call where this occours? By: Matt O'Gorman (mogorman) 2005-10-04 12:03:57 Are you sure this is not intended behavior? I mean if the ivr goes and does the background and then you hit timeout value, and then you don't have a t extension? I mean it should hang up, or is there a misunderstanding in your question. Matt By: Russell Bryant (russell) 2005-10-04 13:51:52 Like mogorman stated, this appears to be a configuration issue. After a timeout, and without handling of the timeout in a 't' extension, the call will end. That's how it is supposed to work. If you feel this is still a problem, you will need to submit your extensions.conf and output from the CLI demonstrating the problem. Thanks. | ||