vicidial.org

[Jul 19 13:01:19] -- Called dialer2:iI0kfj85uqawoXb@50.193.XXX.XXX:4569/8600076
[Jul 19 13:01:19] -- Call accepted by 50.193.XXX.XXX (format ulaw)
[Jul 19 13:01:19] -- Format for call is ulaw
[Jul 19 13:01:19] -- IAX2/dialer1-8612 answered SIP/xcast-0000051b
[Jul 19 13:01:19] -- SIP/xcast-00000540 is ringing
[Jul 19 13:01:19] -- Got SIP response 486 "Busy Here" back from 50.193.XXX.XXX
[Jul 19 13:01:19] -- SIP/xcast-00000519 is busy

So I noticed here that my dialer1 is telling dialer2 to make calls. And that it is using IAX2 instead of SIP? I am just verifying that this is as intended. I just started testing a multi-server setup and want to make sure everything is happening fine. I thought everything would be ran through SIP. I dont have anything that says to use IAX2 that I know of.

All the references to IAX2 in a recent CLI. Not many.
Executing [050*193*XXX*XXX*8600076@default:1] Dial("SIP/xcast-0000051b", "IAX2/dialer2:iI0kfj85uqawoXb@50.193.XXX.XXX:4569/8600076|55|oT") in new stack
IAX2/dialer1-8612 answered SIP/xcast-0000051b
Executing [050*193*XXX*XXX*8600054@default:1] Dial("SIP/xcast-0000052f", "IAX2/dialer2:iI0kfj85uqawoXb@50.193.XXX.XXX:4569/8600054|55|oT") in new stack
IAX2/dialer1-1782 answered SIP/xcast-0000052f
Hungup 'IAX2/dialer1-3843'

1) Welcome to the party! (Although with 64 posts, it looks like you've been here a while and probably already know the next part, but that just raises the question of why you didn't do it in the first place, right? LOL)

2) 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

3) IAX protocol is designed specfically for interasterisk communication (ie: communication between two asterisk servers). Vicidial uses this protocol to "pass" calls between servers. It has no relation to the protocol or codec in use for the other legs of the call.