Dialplan entry for iAX2 tunnel

[vishalchouhan19]

Hi Team,

Device configuration:
PBX1= Vicidial server: V.9.0.0 Asterisk 13.27.0-vici built by abuild @ cloud103 on a x86_64 running Linux on 2019-10-23 03:19:20 UTC
PBX2= Incredible PBX server Asterisk 13.28.0 built by IncrediblePBX.local on a x86_64 running Linux on 2019-08-07 18:17:09 UTC
Extension: 601 (SIP) [Question: Do I need to create iax2 based extension or external for this?]

I am newbie in vicidial, however, I managed to create iax2 tunnel between 2 PBX servers and it is connected. Now , when try to dial out from using softphone with vicidial server or when I run outbound campaign, softconsole says that there is no route to destination. This is happening because I am not shure about dialplan entry. Below is the dialplan I am using on vicidial server:

exten => _1NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _1NXXNXXXXXX,2,Dial(iax2/${EXTEN}@Outgoing_us)
exten => _1NXXNXXXXXX,3,Hangup

I would love to provde you logs for this issue but I am not sure from where I can provide you those. Please let me know the location I will get you those logs to check.
Please help me.

Addiotianlly, do I need to create seperate SIP based trunk to run outbound campaign or to make outgoing call? Ialready have SIP trunk setup on Incredible PBX server.

[williamconley]

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... 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 "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. 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) I REALLY do not recommend trying to use FreePBX (which is what Incredible PBX and it's parent PBX in a flash try to mask: FreePBX under the hood) as a Vicidial server will completely overload a FreePBX server in the same way that you can not tow a Dump Truck with a Smart Car.

4) Logs are at /var/log/asterisk and /var/log/astguiclient for Asterisk and Vicidial respectively. You can also see asterisk logs live as they happen with "asterisk -R" or "screen -r asterisk". However: With screen -r asterisk you must use "ctrl-a" then "ctrl-d" to exit as that's the Live Console (as in if you hit "ctrl-c" instead, you will terminate asterisk and kill all your calls). The "screen -r asterisk" console is necessary sometimes because there are errors that occur in perl code that will not appear anywhere else.

5) For your purpose today, though, we're not really looking for a perl error, just the full details of a single test call from inception to termination. Not 3000 lines of unrelated code, of course, just what is related to that one call with nothing left out.

Happy Hunting!