Cisco Cisco Expressway
Method Request Body
Response
Code
Code
Response
Body
Body
Comment
PUT
{
AuthenticationMode: Controls how Expressway authenticates
incoming messages from this zone and whether they are
subsequently treated as authenticated, unauthenticated, or are
rejected. The behavior varies for H.323 messages, SIP
messages that originate from a local domain and SIP messages
that originate from non-local domains. Default: Do not check
credentials.
incoming messages from this zone and whether they are
subsequently treated as authenticated, unauthenticated, or are
rejected. The behavior varies for H.323 messages, SIP
messages that originate from a local domain and SIP messages
that originate from non-local domains. Default: Do not check
credentials.
AuthenticationUserName: Name used by the traversal client
when authenticating with the traversal server. If the traversal
client is a Expressway, this must be the username configured for
that Expressway's traversal client zone. For other types of
traversal clients, refer to the online help for further information.
Range: 1 to 1024 characters.
when authenticating with the traversal server. If the traversal
client is a Expressway, this must be the username configured for
that Expressway's traversal client zone. For other types of
traversal clients, refer to the online help for further information.
Range: 1 to 1024 characters.
HopCount: Specifies the hop count used when sending an alias
search request to this zone. Note: If the search request comes
from another zone, and already has a hop count assigned, the
lower of the two values is used. Default: 15. Range: 1 to 255.
search request to this zone. Note: If the search request comes
from another zone, and already has a hop count assigned, the
lower of the two values is used. Default: 15. Range: 1 to 255.
Name: Name of the zone. Range: 1 to 1024 characters.
New_Name: Apply a new name to the zone. Range: 1 to 1024
characters.
characters.
Registrations: Controls whether proxied SIP registrations routed
through this zone are accepted. Default: Allow.
through this zone are accepted. Default: Allow.
SIPMediaICESupport: Controls how the Expressway supports
ICE messages to and from the devices in this zone. The behavior
depends upon the configuration of the ICE support setting on
the incoming (ingress) and outgoing (egress) zone or subzone.
When there is a mismatch of settings i.e. On on one side and Off
on the other side, the Expressway invokes its back-to-back user
agent (B2BUA) to perform ICE negotiation with the relevant
host. When ICE support is enabled, you can also configure the
TURN servers to offer as ICE candidates, if necessary. Default:
Off.
ICE messages to and from the devices in this zone. The behavior
depends upon the configuration of the ICE support setting on
the incoming (ingress) and outgoing (egress) zone or subzone.
When there is a mismatch of settings i.e. On on one side and Off
on the other side, the Expressway invokes its back-to-back user
agent (B2BUA) to perform ICE negotiation with the relevant
host. When ICE support is enabled, you can also configure the
TURN servers to offer as ICE candidates, if necessary. Default:
Off.
SIPParameterPreservationMode: Determines whether the
B2BUA in this node preserves or rewrites the parameters in SIP
requests routed via this zone. Default: Off.
B2BUA in this node preserves or rewrites the parameters in SIP
requests routed via this zone. Default: Off.
SIPPoisonMode: Determines whether SIP requests sent out to
this zone are "poisoned" and, if received by the local
Expressway again, then rejected. Default: Off.
this zone are "poisoned" and, if received by the local
Expressway again, then rejected. Default: Off.
SIPPort: Port to use for SIP firewall traversal to and from
traversal client.
traversal client.
SIPPreloadedSipRoutesAccept: Enable this zone to process or
reject SIP INVITE requests that contain Route header. Default:
Off.
reject SIP INVITE requests that contain Route header. Default:
Off.
SIPTLSVerifySubjectName: The certificate holder's name to
look for in the traversal client's X.509 certificate (must be in
look for in the traversal client's X.509 certificate (must be in
200
{
Message:
Success
message
for the
operations.
Success
message
for the
operations.
}
Updates zone
configuration.
configuration.
27
Cisco Expressway REST API Reference Guide
Cisco Expressway-E