Issues with Tutorial F: From Manual

[Kinghtflyer]

ViciBox preload.iso 3.04

Trying to follow the Tutorial in setting up a DID.
I login and click resume.
I dial the Did from my landline.
And I get a fast busy
Asterisk CLI reports,
NOTICE[2603]: chan_sip.c:15741 handle_request_invite: Failed to authenticate user "Unavailable" <sip:5122880391@66.241.96.164>;tag=as73b60155

I can't figure out what is wrong.
I have our provider(vitelity) pointing the DID at my test system.
The call is obviously hitting my server.

Thanks for the help in advance.

[williamconley]

show your carrier configuration (change user/pass to xxx/yyy). matching IP on inbound to a carrier is required. if you do not have a carrier with an ip that matches, there is no way for the asterisk application to know that this call is authorized. if they are sending calls IN from a different IP than you send calls OUT to ... create a new [context] called "[vitel-in]" to hold that new IP (or a list, if they send from more than one ip) for the host=66.241.96.164 entry. that should authorize the call. be sure it has "context=trunkinbound" of course to ensure the call is handled by Vicidial scripts instead of failing in asterisk with nowhere to go.

also:

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

[Kinghtflyer]

Vicibox 3.04 From 64bit-Preload.iso VERSION: 2.8-403a BUILD: 130510-1350 : Asterisk 1.4.44-vici : NO Digium HArdware : Single Server
AMD 8-CORE 4Ghz 16GigRAM : MSI 3070 Mboard : 3-2TB SATA Drives : Disabled RAID : No extra software :

Manager Manual for Vicidial 2.4

Thank you for your response, sorry for my earlier abbreviated configuration.

Our 'production' dialer is 'outbound only'
I took a mysqldump of asterisk from the 'production dialer' and restored to a hardware twin at my residence in an attempt to apply features available only with an inbound route.

I left the outbound credentials 'intact' I'm guessing 'big mistake'
I then set up a sub acct at our provider to 'route' a DID that we only use once a year to that sub acct..

I am grasping here, but if I understand some of what you are trying to tell me, If set up new credentials outbound and inbound that point to the same 'sub acct' on my 'Hardware Twin Server' my problem will probably be resolved?

Excuse my ignorance please.
I am at the production-site Today and am reluctant to do any 'testing' on the operating dialer. I will try resuming my Tutorial F exercise.
Perhaps I will find a way to attend 'Your Vicidial School' September.

My goal is to ultimately get an automated DNC IVR. I have yet figured out how to call the AGI, but until I get inbounds working, that is moot.

[williamconley]

To activate inbound on a system already using outbound, the first step is to get the call to arrive at the dialer. There are two basic ways to accomplish the arrival:

1) Modify a setting in your carrier's web page to "point" the DID to the IP address of your server.

2) Register your vicidial server to an "account" on your carrier's system that already has a DID assigned to it. (Which may also require step one above to "assign" the DID to that "account".)

To validate that the call is arriving at your server, you will need to use the asterisk command line in sip debug mode. If you get ANY activity when you dial the DID, you have succeeded in step one. If you do not get any activity, try to turn off your firewall and test again (avoid doing this during operating hours/times as firewall changes can be disruptive). You can test and turn the firewall back on in a couple minutes total, so a break or lunch are good if you must do this during operating hours.

The next stage involves turning control of the call over to Vicidial (not just asterisk, but to get the Vicidial scripts to control the call so the Web Pages for Vicidial will determine the call route because those web pages write data that the Vicidial scripts read). This is actually quite simple: "context=trunkinbound".

The "context=trunkinbound" should be applied to whatever Admin->Carrier "Account Entry" is used to link to the carrier. If the inbound call is coming from the same address as the outbound calls are sent, then put it in the existing outbound carrier. If not, then create a new [context] (and if you like, a whole new admin->Carrier!) and be sure the "context=trunkinbound" entry is present in the account entry. If you create a whole new carrier for this, leave the "Dialplan Entry" area blank. Inbound carriers can have a "registration string", but it is usually only necessary to have one IF the carrier is not using "IP authentication".

Once this has been done successfully, an inbound call should be answered with "This number is not in sevice, Goodbye!" as that is the default behavior (default DID under Inbound->Show DIDs). This recording playing to the caller, and the associated asterisk command line showing this recording playing, indicates that you have succeeded in configuring your system to receive inbound calls.

Now you read the Vicidial Manager's Manual to figure out how to get it to an agent!

[Kinghtflyer]

Thank you, and the community for the help.

Following Tutorial F: I got inbounds working, then I hit a glitch with Callmenus.
Watching the CLI with an active dialer was keeping me from seeing the debug code. Early this AM I was able to see the output:

format_wav.c:120 check_header_fmt: Unexpected frequency 48000 which told me the boss failed to heed the 8K limit for WAV.
I'm cooking with Gas now.
I can take MysqlDUMP home and load my development box and develop the Call Menus.
Once again, I appreciate your efforts and kindness.

Randy