My outbound calling is not working i get error “file.c:1297 waitstream_core: Unexpected control subclass ‘14’” and “file.c:1297 waitstream_core: Unexpected control subclass '15”
But i get inbound calls, can any body guide me below is my cli output
Created MeetMe conference 1023 for conference ‘8600051’
– <Local/8600051@default-2323,2> Playing ‘conf-onlyperson’ (language ‘en’)
– Executing [8800108424017858@default:1] AGI(“Local/8600051@default-2323,1”, “agi://127.0.0.1:4577/call_log”) in new stack
– AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
– Executing [8800108424017858@default:2] Dial(“Local/8600051@default-2323,1”, “dahdi/g0/08424017858|60|tTo”) in new stack
– Requested transfer capability: 0x00 - SPEECH
– Called g0/08424017858
– DAHDI/1-1 is proceeding passing it to Local/8600051@default-2323,1
– DAHDI/1-1 is making progress passing it to Local/8600051@default-2323,1
[Dec 2 00:07:23] WARNING[22603]: file.c:1297 waitstream_core: Unexpected control subclass ‘15’
[Dec 2 00:07:23] WARNING[22603]: file.c:1297 waitstream_core: Unexpected control subclass ‘14’
== Parsing ‘/etc/asterisk/manager.conf’: Found
You haven’t told us enough about your configuration. In particular, is this analogue or digital. You also haven’[t provided the code of the AGI script or the dialplan.
So the only question is why they are unexpected. That probably depends on what the local channel does. My guess is that you have done an originate to the Local channel and it is playing a message whilst the B leg is being called. In that case the warnings are harmless.
As he is using AGI, he needs to provide the AGI script as well. As I guess he is using originate, he needs to provide details of how this is requested.
Well he can do that but the agi script completes execution and returns back to the dialplan.
What I cannot understand is why a MeetMe conference is being setup at the beginning and then dials out.
It’s not that uncommon for people to ask how to dial a call and then dump it into a conference, but that is being done, in part, in the AGI, making the AGI script important. CORRECTION. It does seem that the AGI script is just logging and done after the conference call is made.
My guess is that he is doing originate to a local channel. The local channel puts itself in the conference, which answers the call. That completes the A side setup for the originate and it starts on the B side. The B side is the dahdi call. The initial call progress signals for the dahdi call arrive during the welcome message for the conference. That code expects to be run on an incoming line, so is surprised by the outgoing call type events and issues warnings, but there is no evidence that anything breaks as a result.
The dahdi call rings out and the log is truncated before it either answers or times out.
Note that the Dial is being run on the ;1 side of the local channel, which pretty much confirms that this is an originate.