Question

Locked

How to set keypad lock for cisco 79xx callpoint?

By emad ·
All employees in the company have cisco callpoint telephone in open area, each employee should lock his callpoint before he leave his desk, How to set keypad lock for cisco 79xx callpoint?
I googled the net but I got no answer!!!

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Go here for your answers..

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7905g_7912g/3_3/h323/english/administration/guide/7905conf.html

This is what you are looking for....

H.323 Gatekeepers

Gatekeepers are primarily responsible for pre-call and call-level control services for H.323 gateways. Gatekeepers are optional components in H.323 systems, When gatekeepers are used in a system, they perform the following call setup and management services:

?Address translation for IP addresses originating from H.323 aliases (address_pool@cisco.com, for example) or E.164 addresses (e.g., standard telephone numbers)

?Admissions control for authorizing or rejecting access to a H.323 zone.

?Bandwidth control for gateway bandwidth requirements

?Zone management for registered voice terminals, gateways and MCUs

Gatekeepers can also provide the following optional functionality:

?Call control signaling using the gatekeeper Routed Call Signaling model

?Call authorization to restrict access to certain voice terminals or gateways or to restrict access based on time-of-day criteria

?Bandwidth management for the H.323 system that will enable the gateway to restrict access when requested bandwidth is unavailable

?Call management including maintaining a list of active calls you can use to indicate available and unavailable voice terminals and gateways

Please post back if you have any more problems or questions.

Collapse -

Can not access User Option Page

by emad In reply to Go here for your answers. ...

Thanks for your reply, now I can not logon to the User Options Page on the CM, whenever I put the user name and password it just shows an error message says "HTTP Status 400 - Invalid direct reference to form login page" any clue how could I avoide this?

Collapse -

HTTP Status 400.. More info on your Status error..

10 Status Code Definitions

Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response.
10.1 Informational 1xx

This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions.

A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent.

Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a

proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).)
10.1.1 100 Continue

The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code.
10.1.2 101 Switching Protocols

The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response.

The protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features.
10.2 Successful 2xx

This class of status code indicates that the client's request was successfully received, understood, and accepted.
10.2.1 200 OK

The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:

GET an entity corresponding to the requested resource is sent in the response;

HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;

POST an entity describing or containing the result of the action;

TRACE an entity containing the request message as received by the end server.
10.2.2 201 Created

The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. The response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server SHOULD respond with 202 (Accepted) response instead.

A 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created, see section 14.19.
10.2.3 202 Accepted

The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.

The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.
10.2.4 203 Non-Authoritative Information

The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Please post back if you have any more problems or questions.

Back to Networks Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums