vicidial.org

When we were using 2.0.4-121 , we used to define VOIP provider details in sip file and dial prefix in extension file.

Now, in 2.0.5 , we have a section as carier where one can define VOIP.

Does that mean we DON'T have to define anything in sip.conf file ?

Exactly, you can define the carrier entirely inside of the web interface.

So, we can use the default sample extension file as it is.

Right ?

So, we install the default Vicidialnow rc1.1 and then can follow the
op3r . com /2009/05/16/vicidial/painless-vicidial-upgrade-from-204-to-205

Also, seen the last line of upgrade document which states to add any customised lines from existing extension to the sample extension file.

I did all these.

But in asterisk cli, when I type dial 912127773456 it doesn't dial out . What could be the possible reason ?

So, we can use the default sample extension file as it is.

Right ?

So, we install the default Vicidialnow rc1.1 and then can follow the
op3r . com /2009/05/16/vicidial/painless-vicidial-upgrade-from-204-to-205

Also, seen the last line of upgrade document which states to add any customised lines from existing extension to the sample extension file.

I did all these.

But in asterisk cli, when I type dial 912127773456 it doesn't dial out . What could be the possible reason ?

What is the Asterisk CLI telling you when you try that?

the problem is.

DONT dial in the asterisk cli when you are using 2.0.5.

Most of the time it just dont work.

Test using your softphone.

and oh somebody reads my blog! thanks!

vicidialnow*CLI> dial 619545090200
No such extension '619545090200' in context 'local'

Justin123 wrote:vicidialnow*CLI> dial 619545090200
No such extension '619545090200' in context 'local'

dial 619545090200@default