<br><br><div><span class="gmail_quote">2006/7/21, David Cook <<a href="mailto:dbc_asterisk@advan.ca">dbc_asterisk@advan.ca</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
From: Filip Dr?gowski <<a href="mailto:f.dragowski@ontp.net">f.dragowski@ontp.net</a>><br>> Subject: Re: [asterisk-users] Two phone numbers, one SIP provider<br>> To: Asterisk Users Mailing List - Non-Commercial Discussion
<br>> <<a href="mailto:asterisk-users@lists.digium.com">asterisk-users@lists.digium.com</a>><br>> Message-ID: <<a href="mailto:44C07951.6040008@ontp.net">44C07951.6040008@ontp.net</a>><br>> Content-Type: text/plain; charset=ISO-8859-2; format=flowed
<br>><br>> I think that context=incoming-[number] in firends definion is used<br>> rather for determinig context for outgoing calls.<br>> In sip.conf [general] section there is context= and<br>> register=>..../[extension]
<br>> i think that extension in register line should be in context specified<br>> in [general] context=[context]<br>><br>>><br>>><br>>>> register => <a href="http://1111:pass@sippro.com/1111">
1111:pass@sippro.com/1111</a><br>>>> register => <a href="http://2222:pass@sippro.com/2222">2222:pass@sippro.com/2222</a><br>>>><br>><br>I am only using inbound IAX but I do have multiple DID's from the same
<br>provider and I hope the action of parsing the files is the same. I don't<br>think you want the extensions listed after the host. The following is<br>what I have for my IAX trunks<br><br>; Registrations for remote IAX servers (dynamic config)
<br>register => <a href="mailto:416xxxxxxx:zzzzz@myprovider.ca">416xxxxxxx:zzzzz@myprovider.ca</a> ; Home line<br>register => <a href="mailto:416yyyyyyy:zzzzz@myprovider.ca">416yyyyyyy:zzzzz@myprovider.ca</a> ; Business line
<br><br>Both calls happily go to contexts [416xxxxxxx] and [416yyyyyyyy]<br>respectively.<br></blockquote></div><br>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.
<br><br>