asterisk users - Jan 2006 - controlling SIP subscriptions from SNOM phones

We recently deployed 10 SNOMs as part of a PBX hosted solution. We have one
phone setup as the receptionist phone, using hints to show busy office
lines. This all works as expected.

This is a new installation, and people are just starting to setup their
phones. For those of you not familiar with SNOM phones, there is a row of
keys on the right side of the phone which SNOM calls function keys. In order
to get the receptionist phone to see the "hinted" extensions, you have
to
set DESTINATION and the extension in the SNOM setup web page. This causes
the receptionist phone to issue SIP SUBSCRIBE messages for the state of
these extensions. 

Now, one user, not the receptionist, has gone in and set his personal
numbers to these function keys thinking that DESTINATION meant setting a
number to dial out. So now I have a ton of SIP SUBSCRIBE messages for his
numbers.

I thought that in order for SIP SUBSCRIBE to work, I had to use 's
"subscribecontext=xxxxx" in the user's config in sip.conf so that
SIP peers
could only subscribe to extensions in that particular context. See the
output below:

asterisk_test*CLI>
     -- Registered SIP '959' at 82.135.81.211 port 5062 expires 3600
     -- Saved useragent "snom320/4.4" for peer 959 Jan  6 20:11:29
ERROR[8677]: chan_sip.c:10790
handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
Please add hint to 008971940494 in context sanset Jan  6 20:11:29
ERROR[8677]: chan_sip.c:10790
handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
Please add hint to 0089956010 in context sanset Jan  6 20:11:29 ERROR[8677]:
chan_sip.c:10790
handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
Please add hint to 904 in context sanset Jan  6 20:11:29 ERROR[8677]:
chan_sip.c:10790
handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
Please add hint to 001708130105 in context sanset Jan  6 20:11:29
ERROR[8677]: chan_sip.c:10790
handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
Please add hint to 001709114321 in context sanset asterisk_test*CLI> sip
show peer 959 asterisk_test*CLI>

   * Name       : 959
   Secret       : <Not set>
   MD5Secret    : <Not set>
   Context      : sanset
   Subscr.Cont. : <Not set>
   Language     : de
   Accountcode  : sanset
   AMA flags    : Unknown
   CallingPres  : Presentation Allowed, Not Screened
   Callgroup    : >
   Pickupgroup  : >
   Mailbox      : 959@sanset
   ...
   SIP Options  : (none)
   Codecs       : 0x100 (g729)
   Codec Order  : (g729)
   Status       : Unmonitored
   Useragent    : snom320/4.4
   Reg. Contact : sip:959@192.168.0.4:5062;line=uq15mxj7

I would think that if there is no subscribecontext set, that Asterisk should
ignore these subscribe messages instead of creating an error. I know that
subscribe is not complete in Asterisk, so I am thinking that this is a bug.

Has anyone else had this same problem? Or know of a way around this? Would
setting the LINE option on the web page work for callout? 

Regards to all,
Joe

It may be better to change it to NOTICE instead of ERROR. You would want
to know it you are trying to subscribe to an unknown 'hint', misconfigs
or lack of should cause NOTICE instead of ERROR.
 
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com 
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Joseph Rothstein
> Sent: Friday, January 06, 2006 2:57 PM
> To: asterisk-users@lists.digium.com
> Subject: [Asterisk-Users] controlling SIP subscriptions from 
> SNOM phones
> 
> We recently deployed 10 SNOMs as part of a PBX hosted 
> solution. We have one phone setup as the receptionist phone, 
> using hints to show busy office lines. This all works as expected.
> 
> This is a new installation, and people are just starting to 
> setup their phones. For those of you not familiar with SNOM 
> phones, there is a row of keys on the right side of the phone 
> which SNOM calls function keys. In order to get the 
> receptionist phone to see the "hinted" extensions, you have 
> to set DESTINATION and the extension in the SNOM setup web 
> page. This causes the receptionist phone to issue SIP 
> SUBSCRIBE messages for the state of these extensions. 
> 
> Now, one user, not the receptionist, has gone in and set his 
> personal numbers to these function keys thinking that 
> DESTINATION meant setting a number to dial out. So now I have 
> a ton of SIP SUBSCRIBE messages for his numbers.
> 
> I thought that in order for SIP SUBSCRIBE to work, I had to 
> use 's "subscribecontext=xxxxx" in the user's config in 
> sip.conf so that SIP peers could only subscribe to extensions 
> in that particular context. See the output below:
> 
> asterisk_test*CLI>
>      -- Registered SIP '959' at 82.135.81.211 port 5062 expires
3600
>      -- Saved useragent "snom320/4.4" for peer 959 Jan  6
20:11:29
> ERROR[8677]: chan_sip.c:10790
> handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
> Please add hint to 008971940494 in context sanset Jan  6 20:11:29
> ERROR[8677]: chan_sip.c:10790
> handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
> Please add hint to 0089956010 in context sanset Jan  6 
> 20:11:29 ERROR[8677]:
> chan_sip.c:10790
> handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
> Please add hint to 904 in context sanset Jan  6 20:11:29 ERROR[8677]:
> chan_sip.c:10790
> handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
> Please add hint to 001708130105 in context sanset Jan  6 20:11:29
> ERROR[8677]: chan_sip.c:10790
> handle_request_subscribe: Got SUBSCRIBE for extensions without hint.  
> Please add hint to 001709114321 in context sanset 
> asterisk_test*CLI> sip show peer 959 asterisk_test*CLI>
> 
>    * Name       : 959
>    Secret       : <Not set>
>    MD5Secret    : <Not set>
>    Context      : sanset
>    Subscr.Cont. : <Not set>
>    Language     : de
>    Accountcode  : sanset
>    AMA flags    : Unknown
>    CallingPres  : Presentation Allowed, Not Screened
>    Callgroup    : >
>    Pickupgroup  : >
>    Mailbox      : 959@sanset
>    ...
>    SIP Options  : (none)
>    Codecs       : 0x100 (g729)
>    Codec Order  : (g729)
>    Status       : Unmonitored
>    Useragent    : snom320/4.4
>    Reg. Contact : sip:959@192.168.0.4:5062;line=uq15mxj7
> 
> I would think that if there is no subscribecontext set, that 
> Asterisk should ignore these subscribe messages instead of 
> creating an error. I know that subscribe is not complete in 
> Asterisk, so I am thinking that this is a bug.
> 
> Has anyone else had this same problem? Or know of a way 
> around this? Would setting the LINE option on the web page 
> work for callout? 
> 
> Regards to all,
> Joe
> 
> _______________________________________________
> --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
>

Hi!
> Now, one user, not the receptionist, has gone in and set his personal
> numbers to these function keys thinking that DESTINATION meant setting a
> number to dial out. So now I have a ton of SIP SUBSCRIBE messages for his
> numbers.
Indeed this situation is not ideal. The first thing to do in my opinion 
is ask SNOM to provide a new type of DESTINATION option that does not 
issue subscribes.

Secondly you need to be aware that if Asterisk doesn't find a matching 
hint in the subscribecontext it will look check in the default context! 
This is, btw, one good reason to not have your local phones in the 
default context unless you want everyone out there to be able to 
subscribe to everyone else...

Finally: Have you tried to create a new context, set the user's 
subscribecontext to this and do a "_.,hint,SIP/DoesNotExist" or smth 
similar within that context (and nothing else)?

Cheers, Philipp