On Wed, 2009-06-03 at 15:28 +0100, Gabor Paller wrote: > One question: let's take your example. > SIP_REGISTRAR_Q.NCH : 0.9=1.0 > > Would that "NCH" be matched against the User-Agent header of the > REGISTER request?
You could define it that way, (see the sipXregistry/lib/register_plugins/mwi/SipImpliedSubscriptions.cpp registry plugin for an example of how), but I'm not sure it's worth the trouble. Do you really want to restrict it (and have it break when the phone vendor changes the UA header) ? The purpose of the .NCH is so that you can have multiple mappings: SIP_REGISTRAR_Q.NCH : 0.9=1.0 SIP_REGISTRAR_Q.ABC : 0.85=1.0 The directive name (all non-blanks before the colon) must be unique; these lines become entries in a hash table internally. You can iterate over all entries that have a common prefix to build up the q-value translation table (again, look at that example for how to read the entries). _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
