2006/7/21, David Cook <[EMAIL PROTECTED]>:
From: Filip Dr?gowski <[EMAIL PROTECTED]>
> Subject: Re: [asterisk-users] Two phone numbers, one SIP provider
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> <[email protected]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-2; format=flowed
>
> I think that context=incoming-[number] in firends definion is used
> rather for determinig context for outgoing calls.
> In sip.conf [general] section there is context= and
> register=>..../[extension]
> i think that extension in register line should be in context specified
> in [general] context=[context]
>
>>
>>
>>> register => 1111:[EMAIL PROTECTED]/1111
>>> register => 2222:[EMAIL PROTECTED]/2222
>>>
>
I am only using inbound IAX but I do have multiple DID's from the same
provider and I hope the action of parsing the files is the same. I don't
think you want the extensions listed after the host. The following is
what I have for my IAX trunks
; Registrations for remote IAX servers (dynamic config)
register => 416xxxxxxx:[EMAIL PROTECTED] ; Home line
register => 416yyyyyyy:[EMAIL PROTECTED] ; Business line
Both calls happily go to contexts [416xxxxxxx] and [416yyyyyyyy]
respectively.
That won't help either. Context is always 'default', but what I want is a different context on any number. Maybe oej's peermatch branch solves the problem. But I cannot compile it, There are lots of '>>>>>> merge right' tags in chan_sip.c.
_______________________________________________ --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
