[asterisk-users] Polycom sip.cfg / voIpProt.SIP.requestValidation.x.request.y.event

Jeff Davis asterisk at netsourceva.com
Sun Jun 10 07:47:52 CDT 2007


Lee Jenkins wrote:
> 
> Hi all,
> 
> My company has pretty much standardized on Polycom phones and I am in 
> the beginning phase of writing a GUI for administering/managing polycom 
> provisioning at multiple sites which we intend to release as OS.

Good luck. I've noticed that Polycom makes changes to the spec on both 
minor and major releases. I don't know how you will account for this, 
but as the saying goes; "Damn it Jim! I an admin not a developer!"

> 
> voIpProt.SIP.requestValidation.x.request.y.event
> 
> I understand what it does (at least conceptually) but ss the "x" 
> variable still referring to a server (1 or 2)?  And the "y" var, what is 
> it referring to?  An event?  Which one?

I believe that the x and y are counters used to group attributes together.

The attribute above; voIpProt.SIP.requestValidation.x.request.y.event, 
depends on voIpProt.SIP.requestValidation.x.request being set to either 
"SUBSCRIBE" or "NOTIFY". Since you SUBSCRIBE to specific events, this is 
a way for the phone to validate either all events, or just those you 
specify. I have not tested the following examples, and welcome any 
correction from someone who has, but this is my understanding of the 
settings.

The default;

<requestValidation
    voIpProt.SIP.requestValidation.1.request=""
    voIpProt.SIP.requestValidation.1.method=""
    voIpProt.SIP.requestValidation.1.request.1.event="">
    <digest voIpProt.SIP.requestValidation.digest.realm="PolycomSPIP" />
</requestValidation>

Could be;

<requestValidation
    voIpProt.SIP.requestValidation.1.request="NOTIFY"
    voIpProt.SIP.requestValidation.1.method=""
    voIpProt.SIP.requestValidation.1.request.1.event="presence">
    <digest voIpProt.SIP.requestValidation.digest.realm="PolycomSPIP" />
</requestValidation>

Or possibly;

<requestValidation
    voIpProt.SIP.requestValidation.1.request="NOTIFY"
    voIpProt.SIP.requestValidation.1.method=""
    voIpProt.SIP.requestValidation.1.request.1.event="presence">
    voIpProt.SIP.requestValidation.1.request.2.event="check-sync">
    <digest voIpProt.SIP.requestValidation.digest.realm="PolycomSPIP" />
</requestValidation>

I believe that you can validate that a check-sync event came from the 
server and not from some other system on the LAN by:

<requestValidation
    voIpProt.SIP.requestValidation.1.request="NOTIFY"
    voIpProt.SIP.requestValidation.1.method="source"
    voIpProt.SIP.requestValidation.1.request.1.event="check-sync">
    <digest voIpProt.SIP.requestValidation.digest.realm="PolycomSPIP" />
</requestValidation>

Please let me know if you discover that I'm wrong about this, but I 
believe that is the way it's supposed to work.

Jeff

--
Jeff Davis
Netsource Consulting


More information about the asterisk-users mailing list