[Home]

Summary:ASTERISK-15705: Allow regcontext per peer
Reporter:Shane Spencer (whardier)Labels:
Date Opened:2010-02-26 18:08:40.000-0600Date Closed:2011-06-07 14:04:50
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/NewFeature
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:If possible can we allow regcontext per peer instead of using a global (in the scope of the channel) regcontext?  This is important if using templates as well as hosting multiple tenants.

I can see how this wouldn't really solve anything if certain peers needed to be registered in multiple contexts.  That would still require a customized regexten per peer.

****** ADDITIONAL INFORMATION ******

We have tentants x, y, and z.

regcontext=xsipregistrations&ysipregistrations&zsipregistrations

[xpeers](!)
[xpeer1](xpeers)
regexten=xpeer1@xsipregistrations
[xpeer2](xpeers)
regexten=xpeer2@xsipregistrations

[ypeers](!)
[ypeer1](ypeers)
regexten=ypeer1@ysipregistrations
[ypeer2](ypeers)
regexten=ypeer2@ysipregistrations

[zpeers](!)
[zpeer1](zpeers)
regexten=zpeer1@zsipregistrations
[zpeer2](zpeers)
regexten=zpeer2@zsipregistrations

It would be nicer if SIP and IAX peers could be configured as follows:

regcontext=xsipregistrations&ysipregistrations&zsipregistrations

[xpeers](!)
regcontext=xsipregistrations
[xpeer1](xpeers)
[xpeer2](xpeers)

[ypeers](!)
regcontext=ysipregistrations
[ypeer1](ypeers)
[ypeer2](ypeers)

[zpeers](!)
regcontext=zsipregistrations
[zpeer1](zpeers)
[zpeer2](zpeers)
Comments:By: Leif Madsen (lmadsen) 2010-03-03 10:02:28.000-0600

While I do like this idea, this is a feature request without a patch, which are not handled on the bug tracker. Please use the asterisk-users or asterisk-biz mailing lists.