Page 1 of 1

Outgoing calls...how do these work?

PostPosted: Tue Feb 19, 2008 11:55 pm
by ykhan
Hi I'm getting this error when I try to make outgoing calls manually from a softphone:

Executing AGI("SIP/CallAgent01-b7a41aa8", "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 Dial("SIP/CallAgent01-b7a41aa8", "provider-outbound/16478915426|55|Tto") in new stack
Feb 19 23:50:26 WARNING[7291]: channel.c:2621 ast_request: No channel type registered for 'provider-outbound'
Feb 19 23:50:26 NOTICE[7291]: app_dial.c:1076 dial_exec_full: Unable to create channel of type 'provider-outbound' (cause 66 - Channel not implemented)
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing Hangup("SIP/CallAgent01-b7a41aa8", "") in new stack
== Spawn extension (default, 916478915426, 3) exited non-zero on 'SIP/CallAgent01-b7a41aa8'
-- Executing DeadAGI("SIP/CallAgent01-b7a41aa8", "agi://127.0.0.1:4577/call_log") in new stack

I've never seen this before, can anyone help on this please? Thanks.

My Bad

PostPosted: Fri Feb 22, 2008 12:16 am
by ykhan
Sorry, I didn't check the most obvious of things. Working fine now.

Hi

PostPosted: Mon Dec 15, 2008 6:08 pm
by gonzalezgjaime
I am a newby on asterisk, and im having the same problem you had 2 years ago, may i ask what were the obvious things that made you dialplan work?

thanks in advance.

Jaime Gonzalez

Re: Outgoing calls...how do these work?

PostPosted: Mon Dec 15, 2008 7:01 pm
by williamconley
ykhan wrote: -- Executing Dial("SIP/CallAgent01-b7a41aa8", "provider-outbound/16478915426|55|Tto") in new stack
Feb 19 23:50:26 WARNING[7291]: channel.c:2621 ast_request: No channel type registered for 'provider-outbound'


not working ... but:
Executing Dial("Local/813214360000@default-9552,2", "SIP/GSM/13214360000||tTo") in new stack


working.

the "channel type" referred to was SIP, but it was in the wrong area of the dial plan. if you do a "scratch-install" clean and test it before moving on to customization, this isn't usually an issue. but if you decide to add your own touches to the system before certifying that it works ... you end up with things like this. (not that *I* have ever done something like that, no way LOL)