On 15:59, Tue 05 Dec 06, Watkins, Bradley wrote:
> You should put all of the 2 thru n priorities in a separate context and
> then include the regcontext into that.
> 
> For example:
> 
> Let's say regcontext = registrations
> 
> And you have a SIP peer:
> 
> [1234]
> type=peer
> ...
> regexten=1234
> 
> You actual dialplan context should look something like:
> 
> [extensions]
> 
> exten => _1XXX,2,Dial(SIP/${EXTEN})
> exten => _1XXX,3,Hangup
> 
> Include => registrations
> 
> 
> 
> Now, when peer 1234 registers, the registrations context will look like:
> 
> [ Context 'registrations' created by 'SIP' ]
>   '1234' =>         1. NoOp()                                   [SIP]
> 
> 
> 
> And, since the 'extensions' context includes 'registrations', any calls
> that originate in 'extensions' will succeeed where they will not if 1234

DUH.
Thnx for the reply. the sollution is plain simple. Think my
brain is on holiday or something.

-- 

Michiel van Baak
[EMAIL PROTECTED]
http://michiel.vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD

"Why is it drug addicts and computer afficionados are both called users?"

_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to