Summary:	ASTERISK-05014: [request] [post 1.2] - Implement "hintexten" sip peer setting
Reporter:	Vahan Yerkanian (vahan)	Labels:
Date Opened:	2005-09-07 06:46:11	Date Closed:	2011-06-07 14:03:06
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Subscriptions
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	As per http://www.voip-info.org/tiki-index.php?page=Asterisk%20presence exten => 1234,hint,SIP/1234 works, But if you try to register multiple extensions using a wildcard: exten => _1XXXX,hint,SIP/${EXTEN} it doesn't work.
Comments:	By: Olle Johansson (oej) 2005-09-07 07:34:54 Thinking about this, it is not easily possible. Sorry. The ${EXTEN} is executed at runtime of the dialplan and the hint is not really part of any execution. So we can't do it the way "normal" extensions work. The only way would be to save these to after loading the dial plan, then do all the matching and add all the hints after we've created the dial plan. I don't think that's a good solution either. What about doing it the other way, adding a "hintexten" to the peer entry in sip.conf - and let chan_sip create the hint in the dialplan for that extension when we load the peer? That would work well for static peers, but I guess not for dynamic peers until they actually register with Asterisk. Regardless, it's a possible solution. /Olle By: Vahan Yerkanian (vahan) 2005-09-07 07:43:22 I agree, that's much a nicer way of handling the hint - after all each peer has 1 hint, so it is better to make the hint a peer entry. Should be easy also if you are using sip_buddies kind of thing - just alter the table and add the 'hintexten' column. By: Olle Johansson (oej) 2005-09-07 07:56:45 Ok, moving this to feature requests that will be looked at after 1.2. By: Kevin P. Fleming (kpfleming) 2005-12-01 21:29:36.000-0600 There is no practical way to implement this, because it would severely harm the performance of hints and device state notifications. The pattern matching would have to happen far too often... By: Kevin P. Fleming (kpfleming) 2005-12-01 21:31:10.000-0600 OK, so now I see that the summary of this issue has been changed without changing the description... never mind :-) If this was to be implemented, it would require both a hintexten and a hintcontext. By: Vahan Yerkanian (vahan) 2005-12-02 03:28:50.000-0600 Would it be possible and adequate to move the hinting to the sip.conf / realtime db, adding it as a hint=SIP/1234 to the user entry? something like [1234] username=1234 secret=4567 hint=SIP/1234 By: Olle Johansson (oej) 2005-12-02 10:08:29.000-0600 No, the hint has to define which extension and context to place the hint in or add the hint to if it is already there. We already know the device name - it's the peer name we are configuring :-) By: opsys (opsys) 2005-12-30 18:16:48.000-0600 HOUSEKEEPING: Can we close this?? By: Matt O'Gorman (mogorman) 2006-01-11 18:39:55.000-0600 i vote for closeure as well By: Olle Johansson (oej) 2006-01-12 01:51:26.000-0600 Let's close this as a feature request and open again if we have code.