Trunk between two ViciDial

[Paul001]

Hi

I need make a trunk between two ViciDial (VERSION: 2.4-309a - BUILD: 110430-1642)
This si de configuration but this fails. Please help me.

Server 1:
192.168.92.11
Extension: 8001-8020


Carrier ID: sipexample
Carrier Name: sipexample

Carrier Description:

Registration String: register => sipexample:test@192.168.92.20:5060

Template ID:

Account Entry:
[sipexample]
fromuser=sipexample
disallow=all
allow=ulaw
type=peer
username=sipexample
secret=test
host=192.168.92.20
context=trunkinbound

Protocol:
IAX2

Globals String:
TESTSIPTRUNK = IAX2/sipexample

Dialplan Entry:
exten => _4XXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _4XXX,2,Dial{${TESTSIPTRUNK}/${EXTEN},60,tTo)
exten => _4XXX,3,Hangup

Server IP: 192.168.92.11
Active: YES



Server 2:
192.168.92.20
Extension: 4001-4020


Carrier ID: sipexample
Carrier Name: sipexample

Carrier Description:

Registration String: register => sipexample:test@192.168.92.11:5060

Template ID:

Account Entry:
[sipexample]
fromuser=sipexample
disallow=all
allow=ulaw
type=peer
username=sipexample
secret=test
host=192.168.92.11
context=trunkinbound

Protocol:
IAX2

Globals String:
TESTSIPTRUNK = IAX2/sipexample

Dialplan Entry:
exten => _8XXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _8XXX,2,Dial{${TESTSIPTRUNK}/${EXTEN},60,tTo)
exten => _8XXX,3,Hangup

Server IP: 192.168.92.20
Active: YES

[williamconley]

1) This is not a "general discussion", it's a support question, so I moved it. Appropriate people will more likely see it.

2) Welcome to the party!

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

4) When your "8XXX" or "4XXX" call arrives at the receiving server, it will land in the "trunkinbound" context in extensions.conf. This may not be the desired behavior as this will then require a DID pointed to wherever you want each call to go ... on the other hand, if you are prepared to set up DIDs to point the calls, you're good to go. If, however, you simply want the extension to be "dialed" upon arrival, you may want to change the "context=" to "default" in each of them.

5) WHY are you "linking them" in this fashion instead of building a Cluster? (Which has an option to build inter-server extensions ...).