Summary:	ASTERISK-06937: subscriptions do not work if sipdomains are used
Reporter:	raarts (raarts)	Labels:
Date Opened:	2006-05-09 14:46:28	Date Closed:	2006-05-19 14:43:41
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Subscriptions
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	In sip.conf I use: [example-3000] type=friend context=phone subscribecontext=example-subscribe [example2-3000] type=friend context=phone subscribecontext=example2-subscribe and subscriptions worked great. Then I wanted to support incoming SIP urls and I added the following to the [general] section domain=example.com,example-inbound domain=example2.com,example2-inbound domain=192.168.1.9,phone and added the namepart of the sip url as extensions to the dialplan. This worked beautifully, but now subscriptions have stopped working. Probably because of the line "domain=192.168.1.9,phone" all subscriptions are searched only on the [phone] context. But I can't get SIP URL's to work otherwise, because phone won't register without the third domain line. Shouldn't subscribecontext be the third parameter of a domain= statement?
Comments:	By: Joshua C. Colp (jcolp) 2006-05-19 13:05:25 I really don't know what the right behavior should be, but your title is misleading - it's not broken... it just doesn't work as you think it should. Let's see if oej can shed some light on things! By: Russell Bryant (russell) 2006-05-19 13:06:11 It seems to me that added a 3rd parameter to the domain statement to specify a subscribe context would be reasonable, but this is not really something that will happen for 1.2 Looking ahead for 1.4, does it make sense to have domain settings always override the settings specific to a peer?  It seems to me that if a context or subscribecontext is specified specific to a peer, that it should have higher precedence than the default settings for a domain.  However, this is not currently the case.  This also may be a misunderstanding on my part for how the domain support is supposed to work. We are going to need some input from oej on this one. By: Kevin P. Fleming (kpfleming) 2006-05-19 14:43:40 Fixed in branch 1.2 revision 28794 and trunk revision 28795.