On Thu, Sep 30, 2010 at 9:56 AM, Henry Coleman <[email protected]>wrote:
> I don't think that will work. The assignment of a guiding number is > directly related to a specific channel > > ie. In "ZAP Channel DIDs" menu CH1 is set to 4165551212 (ANI) and labelled > "ZapCH1_4165551212". In Inbound Routes you create a route "4165551212 /Any > CID" that can route that specific channel > to an extension or ring group etc. > To select a specific channel for outgoing routes you must use the dial plan > in outgoing routes: > > all local calls (416NXXXXXX) use the assigned trunk > label "ZapCH1_4165551212" > but more likely you want it to select the first available trunk starting at > the CH4 position (which is available using groups) ie G0 > > Hope this helps > > H > > > On Wed, Sep 29, 2010 at 6:08 PM, Yajie <[email protected]> wrote: > >> Hi David, >> >> Thanks you for you input. So in my FreePBX trunk configuration, Can i >> use g0/1, g0/2 ... in Zap Identifier field to specify which channel i am >> going to use in particular trunk? >> >> Yajie >> >> On Tue, Sep 28, 2010 at 10:34 PM, David Cook <[email protected]> >> wrote: >> >> > Yes you can use each of the lines independently but that would be >> missing >> > part of the power of a PBX over that of a key system. >> > (Key system is where you select which line you want to use before >> > initiating >> > the call. A PBX does the search/picking of the line for you). >> > >> > You can access the individual ports as DAHDI/1 or DAHDI/2, etc. but you >> can >> > get into complex logic of how you pick line 1 over line 2 and how to >> tell >> > if >> > the selected line is busy, what to do when it is, etc. >> > >> > As opposed to them also being in the group G0 meaning calls to DAHDI/G0 >> > will >> > pick the first available line. This makes it much easier for the user >> when >> > the switch does the work for you. (Unless of course the different lines >> > have >> > different calling or pricing rules). If that is the case then you should >> > group them according to such policies but still arrange them in groups. >> > >> > - dbc. >> > -----Original Message----- >> > From: [email protected] [mailto:[email protected]] >> > Sent: September-28-10 9:55 PM >> > To: garry liu >> > Cc: [email protected] >> > Subject: Re: [on-asterisk] how to use the second channel of my sangoma >> B600 >> > card >> > >> > Thanks a lot for your reply. Does this mean I can't pick which of the >> four >> > fxo lines to make outbound calls? That is kind of disappointing b/c I >> was >> > planing to have two bell lines and give user ability to choose which >> line >> > to >> > go out. >> > >> > Yajie >> > Sent from my BlackBerry device on the Rogers Wireless Network >> > >> > -----Original Message----- >> > From: garry liu <[email protected]> >> > Date: Wed, 29 Sep 2010 08:17:06 >> > To: Yajie<[email protected]> >> > Cc: <[email protected]> >> > Subject: Re: [on-asterisk] how to use the second channel of my sangoma >> B600 >> > card >> > >> > Hi Yajie, >> > >> > Sangoma B600 is a (4 FXO and 1FXS) card, and I guess your G0 is the >> group >> > of 4 FXO and G1 1 FXS. Only way is to make outbound calls through FXOs. >> > Check your dial plan. >> > >> > Good Luck, >> > >> > Garry >> > On Wed, Sep 29, 2010 at 7:49 AM, Yajie <[email protected]> wrote: >> > >> > > i am using sangoma B600 card, i can make outbound call with the first >> ZAP >> > > trunk(g0) , but not the second ZAP trunk (g1), what have i done wrong? >> > > >> > > >> > > >> > > >> > > Using my g1 trunk,(failed) >> > > >> > > -- Executing [...@macro-dialout-trunk:19] Dial("SIP/300-0a06e160", >> > > "DAHDI/g1/4166409294|300|") in new stack >> > > -- Called g1/4166409294 >> > > -- DAHDI/5-1 is ringing >> > > -- DAHDI/5-1 is ringing >> > > -- DAHDI/5-1 is ringing >> > > -- DAHDI/5-1 is ringing >> > > -- Remote UNIX connection >> > > -- Remote UNIX connection disconnected >> > > -- DAHDI/5-1 is ringing >> > > -- DAHDI/5-1 is ringing >> > > -- DAHDI/5-1 is ringing >> > > -- DAHDI/5-1 is ringing >> > > -- Hungup 'DAHDI/5-1' >> > > == Spawn extension (macro-dialout-trunk, s, 19) exited non-zero on >> > > 'SIP/300-0a06e160' in macro 'dialout-trunk' >> > > >> > > >> > > >> > > Using my g0 trunk (succeed) >> > > - Executing [...@macro-dialout-trunk:19] Dial("SIP/300-b7b160b0", >> > > "DAHDI/g0/4166409294|300|") in new stack >> > > -- Called g0/4166409294 >> > > -- DAHDI/2-1 answered SIP/300-b7b160b0 >> > > >> > > >> > > >> > > >> > > -- >> > > Yajie >> > > >> > >> > >> > >> >> >> -- >> Yajie >> > > > > -- > *Henry L. Coleman * > ***Per: VoIP-PBX.ca > * > * > * > > > -- *Henry L. Coleman * ***Per: VoIP-PBX.ca * * *
