[asterisk-gui] Trunks/Service Providers

Trevor Benson tbenson at a-1networks.com
Tue Oct 14 13:34:57 CDT 2008


> I'm not very familiar with the features provided by the gui, so I'm
> just
> thinking in terms of the underlying config file architecture. But I
> think
> you are right in that you just do trunk, not service provider.

Yeah I know how to do it in the configs without any issues, we trunk a bunch
of call center systems together, clients to our system, etc.  Its specific
to the GUI that I am trying to correlate to the configs, that way I can
connect 2 GUI systems, and a GUI to a non GUI without being confused.

> You still need to have user names, because that is how the calling end
> specifies which section of the called end's iax.conf will be used:
> [user]
> 
> So if you initiate a call to IAX/foo/12345, that will use the section
> called [foo] in the calling system's iax.conf:
> 
> [foo]
> type=peer
> host=11.22.33.44
> username=bar
> secret=barpw
> peercontext=barcon
> 
> In the called system's iax.conf it will need:
> 
> [bar]
> type=user
> secret=barpw
> context=barcon
> deny=0.0.0.0/0.0.0.0
> allow=55.66.77.88
> 
> Where 11.22.33.44 is the called system's IP and 55.66.77.88 is the
> calling
> system's IP. The call will then be routed to extension 12345 in the
> context [barcon] in the called system's dialplan.
> 
> As far as I know, the called end's "context=barcon" doesn't remove the
> need
> for "peercontext=barcon" at the calling end, but rather just adds
> barcon
> to the list of permitted contexts. (anyone else feel free to correct!)
> 
> Cheers
> Tony
> 
> >
> > > -----Original Message-----
> > > From: asterisk-gui-bounces at lists.digium.com [mailto:asterisk-gui-
> > > bounces at lists.digium.com] On Behalf Of Tony Mountifield
> > > Sent: Friday, October 10, 2008 3:26 AM
> > > To: asterisk-gui at lists.digium.com
> > > Subject: Re: [asterisk-gui] Trunks/Service Providers
> > >
> > > In article <013e01c92a3c$4dc59ad0$e950d070$@com>,
> > > Trevor Benson <tbenson at a-1networks.com> wrote:
> > > > I know this sounds sort of mundane, but can someone give me a
> brief
> > > example
> > > > of how service providers and trunks in Asterisk GUI 2 are used? I
> > > setup
> > > > trunks between systems all the time, and using the trunks
> interface
> > > of the
> > > > GUI I always seem to run into some weird thing where I am not
> placing
> > > the
> > > > correct values in each side.
> > > >
> > > > I am assuming that 2 systems will be trunked on IAX, and
> registering
> > > to
> > > > eachother.  Each one will have its own usename and password for
> the
> > > > registration phase.  Thus HostA would send 'HostA' as its user
> with a
> > > > password, and HostB would send 'HostB' as the user and password.
> > > >
> > > > Am I missing something?  It just seems like the GUI wants a
> single
> > > username
> > > > and password for both sides, or am I just not grasping how its
> > > setting up
> > > > the 'service provider' or trunks?
> > >
> > > As I understand it, registration is only required when a host on a
> > > dynamic
> > > IP address needs to inform the other end of that IP (in order to
> > > satisfy a
> > > host=dynamic, so that the fixed host can initiate calls to the
> dynamic
> > > one).
> > >
> > > So having both ends of a link register to each other doesn't make
> > > sense,
> > > since at least one end must be on a known fixed IP address.
> > >
> > > If both ends are on fixed IPs, just specify those IPs in the iax
> > > contexts
> > > and don't bother with registration at all.
> > >
> > > Or is there another factor in registration that I have missed?
> > >
> > > Cheers
> > > Tony
> > > --
> > > Tony Mountifield
> > > Work: tony at softins.co.uk - http://www.softins.co.uk
> > > Play: tony at mountifield.org - http://tony.mountifield.org
> > >
> > > _______________________________________________
> > > --Bandwidth and Colocation Provided by http://www.api-digital.com--
> > >
> > > asterisk-gui mailing list
> > > To UNSUBSCRIBE or update options visit:
> > >    http://lists.digium.com/mailman/listinfo/asterisk-gui
> > >
> > >
> > > __________ Information from ESET NOD32 Antivirus, version of virus
> > > signature database 2806 (20080118) __________
> > >
> > > The message was checked by ESET NOD32 Antivirus.
> > >
> > > http://www.eset.com
> > >
> >
> >
> > __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> > database 2806 (20080118) __________
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
> > _______________________________________________
> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
> >
> > asterisk-gui mailing list
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-gui
> >
> 
> 
> --
> Tony Mountifield
> Work: tony at softins.co.uk - http://www.softins.co.uk
> Play: tony at mountifield.org - http://tony.mountifield.org
> 
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> 
> asterisk-gui mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-gui
> 
> 
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 2806 (20080118) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
> 




More information about the asterisk-gui mailing list