Well, after very quickly making a test call it's not Vitelity. It could be
something with your account? Might want to try opening a support ticket. If
you want, create a sub account and e-mail me off list the username and
password and I'll test it with my box or vice versa.
On Tue, Oct 7, 2008 at 10:38 AM, Stephen Reese <[EMAIL PROTECTED]> wrote:
> > The voicemail command should be Voicemail([EMAIL PROTECTED]) so in
> > extensions.conf
> > exten => 101,n,Voicemail([EMAIL PROTECTED])
> > As for the console when you launch it add v's to set the debugging level
> > 'asterisk -vvvvvr' you can also run 'core set debug X' X=debug level 0-10
> I
> > believe. Just to make sure, you are doing a 'module reload' each time you
> > make changes to configuration files right?
>
> Cool I've got voicemail :-). I am reloading it and have increased the
> logging level.
>
> When dialing out I'm seeing:
>
> -- Executing Dial("SIP/101-08183018",
> "SIP/[EMAIL PROTECTED]") in new stack
> -- Called [EMAIL PROTECTED]
> -- SIP/vitel-outbound-0818b178 is circuit-busy
> == Everyone is busy/congested at this time (1:0/1/0)
> Oct 7 10:34:34 WARNING[6465]: pbx.c:2435 __ast_pbx_run: Timeout, but
> no rule 't' in context 'default'
>
> Think it's a problem with vitelity?
>
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
