Is VICIDIALNOW already a SIP server?

[Winux]

Thought SIP servers is to provide name resolution and user location because caller is unlikely to know the IP address or host name of the called party, But want is important is : How to configure the SIP.CONF?
A technical guide about the modification to be done on the file is required for any newbies i think!
THANKS IN ADVANCE ALL THE EXPERIENCED GUYS HOLDING EFLO.NET.

[williamconley]

anyone interested, of course, would look to asterisk manuals for configuring sip.conf, or use vicibox which will do it for you (for the agents, at least).

as far as configuring trunks, of course, that's back to asterisk and/or the "samples" in the GUI version of 2.0.5 and above under admin->carriers.

[Op3r]

as for the technical guide the manual is available at www.eflo.net/store.php .

This will enable you to properly administer VICIDIAL. And yes there's a tutorial for the configuration of sip trunking.

Once my mastery of english language is sufficient, Im planning submit a tutorial for the inclusion of the manual. (yes Ill do this in return of a free manual? *wink to matt)

all in all the Manual is all you need to save effort, your job security, the ease of operation and possible it will even save you with more sleep!

[williamconley]

i agree. i tell every client to purchase a manual and charge a serious amount of money to answer questions when they are IN the manual. some clients don't care, they want it to work without touching (i'd say they belong in the microsoft world, but they pay me to keep them away from the licensing monsters, and in the end they still spend less than 25%, even with support from me to allow them to be virtually hands-off)

[mflorell]

I will be working on the 2.2.0 manuals shortly, if you would want another tutorial added I'm all ears

[williamconley]

yeah, how about a "troubleshooting wizard", who's building THAT?

[Op3r]

I am trying to scan my emails now about that "what to do in case this happens" tutorial I created.

Sorry for the hijack thread.

Anyway, I am going to use 2.2.0 this week on my own call center to test and learn. Nothing beats using a not yet touched vicidial version than on production

VICIDIAL really come a long way. I remember I used to have problems every single hour while on operation. and all I used to know was reboot reboot reboot! which always work though. Really the software is maturing is conjunction of my own vicidial maturity.

Yet, I never thought owning a call center eats a lot of my time My center never experienced any problems on the technical side (except somebody forgot to reset the leads hence the long wait) its the operation side that is pissing me off. :0