Summary: | ASTERISK-06327: Channel moving goes bad | ||
Reporter: | Edwin Groothuis (mavetju) | Labels: | |
Date Opened: | 2006-02-15 18:16:43.000-0600 | Date Closed: | 2011-06-07 14:03:23 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) extensions.conf ( 1) today.txt | |
Description: | At http://www.mavetju.org/~edwin/today.txt (also attached) I have a snippet of a logfile of a asterisk server running tuesdays 1.2 branch, but it already happened in earlier 1.2.3 and 1.2.4 versions. The interesting part about this snippet is that it failed to properly connect the two channels. Short story: - at 11:25:20, 02 9335 3047 calls 0409 227 633 and it rings - at 11:25:22, 02 8226 2301 calls 0410 471 000 and it rings - at 11:25:26, the second call tries to move it to the channel of the first call (which fails, because it is in use etc etc etc) - at 11:25:27, the first call tgries to move it to the channel of the second call (which fails too!) after that, and this is hearsay because the logs don't show it, the first caller gets connected to the second called. What is going wrong here, at 11:25:26 and at :27, is that it tries to move it between channels. I'm not sure why it does do that, but that is where it goes wrong. More information (tons of it) can be supplied. | ||
Comments: | By: Tilghman Lesher (tilghman) 2006-02-16 16:46:14.000-0600 We're going to need to see your entire extensions.conf. By: Edwin Groothuis (mavetju) 2006-02-16 17:27:57.000-0600 I have uploaded my extensions.conf to http://www.mavetju.org/~edwin/extensions.conf. It doesn't contain the #include files which are just giant repetitions of numbers. A call comes in via the context SJH-A44001, and goes to the PSTN via the include barnet-call-ext-sjh, which calls the macro-call-ext-sjh, which calls the macro-call-ext-XXX, which does do the real call. By: Mark Spencer (markster) 2006-02-20 08:18:08.000-0600 Please pursue this through Digium technical support. If you are unable to resolve your issue there, feel free to contact me off the bug tracker. |