No subject

> The phones are ringing at this point. In the logs I see this:
> 
> [2012-04-12 08:51:06] DEBUG[7313] sig_analog.c: analog_exception 1
> [2012-04-12 08:51:06] DEBUG[7313] sig_analog.c: Exception on 13, channel 1
> [2012-04-12 08:51:06] DEBUG[7313] sig_analog.c: __analog_handle_event 1
> [2012-04-12 08:51:06] DEBUG[7313] sig_analog.c: Got event ANALOG_EVENT_RINGBEGIN(12) on channel 1 (index 0)
> 
> I'm assuming the indication 3 specified earlier was to send ring
> tones on DAHDI/1, this simply confirms it?

This is chan_dahdi reporting the event from the kernel drivers that
the FXO port is starting another RING cycle. Depending on how your
dialplan is written, the originating channel won't be answered until
one of the endpoints answer.

> Next, one of the phones answered the call, and a new indication is sent:
> 
> [2012-04-12 08:51:07] VERBOSE[7313] app_dial.c:     -- SIP/102-000021ae answered DAHDI/1-1
> [2012-04-12 08:51:07] DEBUG[7313] chan_dahdi.c: Requested indication 22 on channel DAHDI/1-1
> 
> What does indication 22... indicate?

This is chan_dahdi being told that one of the SIP phones has picked
up the call. From AST_CONTROL_CONNECTED_LINE in
include/asterisk/frame.h

> There is more to the log, but it is intermingled with a callback
> and I'm not easily able to parse it out at the moment. Does any of
> the above seem out of place, or does it look 'normal'?

This all looks pretty normal to me.

> As an aside, where could a person find a list of indications used
> on DAHDI channels, analog and/or PRI/T1?

I'm not sure if there is any place where they are all listed out
besides in the source code.

-- 
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org