As I understand it (and my understanding is obviously incorrect) the switch => statement sells the Asterisk box to resolve (aka lookup) extensions by querying the remote Asterisk server defined in the switch => statement. The switch => statement is used to centralize dialplans. I've not used the switch => statement yet, I'm just trying to understand the ramifications of using it before I try it and blow up my dial plan. Here's an example of a sample setup Asterisk Server ast-1 switch => IAX/bobdobbs@ast-2 Asterisk Server ast-2 exten => 12010,1,Dial(Zap/1) If I'm on a device connected to ast-1 and I dial 12010 I assume ast-1 asks ast-2 to resolve the extension 12010, and I also assume that ast-2 returns "exten => 12010,1,Dial(Zap/1)" then ast-1 tries to Dial(Zap/1) which is not an interface on ast-1 and the call fails. What information am I missing? --Eric -- BTEL Consulting 850-484-4535 x2111 (Office) 504-595-3916 x2111 (Experimental) 877-552-0838 (Backup Phone)
You're missing that then the IAX call will be started between ast1 and ast2 and you'll get connected to ast2 Zap/1 Martin On 13 Jun 2003, Eric Wieling wrote:> As I understand it (and my understanding is obviously incorrect) the > switch => statement sells the Asterisk box to resolve (aka lookup) > extensions by querying the remote Asterisk server defined in the switch > => statement. The switch => statement is used to centralize dialplans. > > I've not used the switch => statement yet, I'm just trying to understand > the ramifications of using it before I try it and blow up my dial plan. > > Here's an example of a sample setup > > Asterisk Server ast-1 > switch => IAX/bobdobbs@ast-2 > > Asterisk Server ast-2 > exten => 12010,1,Dial(Zap/1) > > If I'm on a device connected to ast-1 and I dial 12010 I assume ast-1 > asks ast-2 to resolve the extension 12010, and I also assume that ast-2 > returns "exten => 12010,1,Dial(Zap/1)" then ast-1 tries to Dial(Zap/1) > which is not an interface on ast-1 and the call fails. > > What information am I missing? > > --Eric > > > > > -- > BTEL Consulting > 850-484-4535 x2111 (Office) > 504-595-3916 x2111 (Experimental) > 877-552-0838 (Backup Phone) > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users >
Yes, that's right, but you might need to use: switch => IAX2/user:pass@host/context Mark On 13 Jun 2003, Eric Wieling wrote:> As I understand it (and my understanding is obviously incorrect) the > switch => statement sells the Asterisk box to resolve (aka lookup) > extensions by querying the remote Asterisk server defined in the switch > => statement. The switch => statement is used to centralize dialplans. > > I've not used the switch => statement yet, I'm just trying to understand > the ramifications of using it before I try it and blow up my dial plan. > > Here's an example of a sample setup > > Asterisk Server ast-1 > switch => IAX/bobdobbs@ast-2 > > Asterisk Server ast-2 > exten => 12010,1,Dial(Zap/1) > > If I'm on a device connected to ast-1 and I dial 12010 I assume ast-1 > asks ast-2 to resolve the extension 12010, and I also assume that ast-2 > returns "exten => 12010,1,Dial(Zap/1)" then ast-1 tries to Dial(Zap/1) > which is not an interface on ast-1 and the call fails. > > What information am I missing? > > --Eric > > > > > -- > BTEL Consulting > 850-484-4535 x2111 (Office) > 504-595-3916 x2111 (Experimental) > 877-552-0838 (Backup Phone) > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users >