Re: [sipX-dev] call pickup codes validation

["Picher, Michael" <mpicher@xxxxxxxx>]

>From an implementation point of view though, if we want to disable
global pickup or avoid accidental global pickup it would be better to
have it be a different *nn code.

Thanks,
  Mike

-----Original Message-----
From: sipx-dev-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:sipx-dev-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Lih Tzeng
Sent: Tuesday, April 17, 2007 10:20 AM
To: 'Douglas Hubler'; 'Damian Krzeminski'
Cc: sipx-dev@xxxxxxxxxxxxxx
Subject: Re: [sipX-dev] call pickup codes validation

> -----Original Message-----
> From: sipx-dev-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:sipx-dev-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Douglas Hubler
> >
> > Directed call pickup code is just a prefix. *78123 would 
> pickup 123 extension.
> > *78 by itself is not an entire feature code.
> > sipXconfig will have to know which codes require further 
> parameter to check for conflicts.
> >   
> So could I configure SIP_PRESENCE_SIGN_IN_CODE to *78 and it 
> wouldn't conflict with call pickup because there are no 
> trailing digits?

  The purpose of having a fixed syntax, *nn, is to avoid conflict
  by just checking three characters, *nn.  If there is no conflict
  in this restricted *nn space, there should not be any conflict
  in *nnyyyy... space where yyyy... are the trailing digits following
  the feature code *nn.  Therefore, checking the uniqueness of *nn
  is sufficient IMHO.


_______________________________________________
sipx-dev mailing list
sipx-dev@xxxxxxxxxxxxxxxxxxx
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev