Hi,
What can I make of the following log messages? Extension 7114 tries to reach
6035 but gets an "unknown channel type". What does it mean?
(supposedly, 6035 was not busy...)
Apr 12 13:01:01 VERBOSE[30989] logger.c: -- Executing
Dial("SIP/7114-b4fe1ef0", "/6035|300|") in new stack
Apr 12 13:01:01 WARNING[30989] channel.c: No channel type registered for
''
Apr 12 13:01:01 NOTICE[30989] app_dial.c: Unable to create channel of type
'' (cause 66 - Channel not implemented)
Apr 12 13:01:01 VERBOSE[30989] logger.c: == Everyone is busy/congested at this
time (1:0/0/1)
Thanks
Vieri
----- "Vieri" <rentorbuy at yahoo.com> wrote:> Hi, > > What can I make of the following log messages? Extension 7114 tries to > reach 6035 but gets an "unknown channel type". What does it mean? > (supposedly, 6035 was not busy...) > > Apr 12 13:01:01 VERBOSE[30989] logger.c: -- Executing > Dial("SIP/7114-b4fe1ef0", "/6035|300|") in new stack > Apr 12 13:01:01 WARNING[30989] channel.c: No channel type registered > for '' > Apr 12 13:01:01 NOTICE[30989] app_dial.c: Unable to create channel of > type '' (cause 66 - Channel not implemented) > Apr 12 13:01:01 VERBOSE[30989] logger.c: == Everyone is > busy/congested at this time (1:0/0/1) >You didn't specify a channel type for extension 6035 hence the empty '' and subsequent call failure. Update your dialplan to reflect SIP/6035 or IAX2/6035 or CARRIERPIGEON/6035... --Tim