|
|
|
|
|
3M Standard Interchange Protocol (SIP)Minimum version requiredThe options described in this document require EZproxy 2.4c (2003-03-21) or later, with the exception of the SIP2 directive which requires EZproxy 4.0g (2007-03-12) or later. All options
The SIP directive tells EZproxy to use SIP1 when communicating with the remote host. The SIP2 directive appears in EZproxy 4.0g (2007-03-12) or later to use SIP2 protocol. When configuring, you should use either the SIP or SIP2 directive, but not both. Whether using the SIP or SIP2 directive, the entry in user.txt/ezproxy.usr always starts with ::SIP and always ends with /SIP. Socket connection with no authenticationFor SIP1, use:
For SIP2, use:
The remainder of the example use the SIP directive for SIP1. You can substitute SIP2 in any of these examples of SIP2. Socket connection with no authentication using SIP1
Socket connection with SIP username and password
Telnet connection
In the previous example, the username and password used to access SIP are sent as part of the telnet connection. The \n that appears in this example indicates that a newline should be sent, similar to pressing the enter key at the end of a line. If your SIP server requires a password during SIP negotiation, you can use an entry similar to this next example. Telnet connection with SIP username and password
|