H.323 Protocol Parameters

Use the parameters in the following table to:
  • Configure SIP and H.323 protocols
  • Set up a SIP and H.323 dial plan

    Numbers with the format 0xxx are placed on a SIP line and numbers with the format 33xx are placed on an H.323 line.

  • Set up manual protocol routing using soft keys

    If the protocol to use to place a call cannot be determined, the Use SIP and Use H.323 soft keys display, and users must select one to place the call.

  • Configure auto-answering on H.323 calls only.
  • Set the preferred protocol to SIP.
  • Set to configure one SIP line, one H.323 line, and a dual protocol line—both SIP and H.323 can be used.
  • Set the preferred protocol for off-hook calls on the third (dual protocol) line to SIP.
    Table 1. H.323 Protocol Parameters

    Template

    Parameter

    Permitted Values

    Change Causes Restart or Reboot

    features.cfg

    up.manualProtocolRouting

    Specifies whether to choose a protocol routing or use a default protocol.

    1 (Default) - User is presented with a protocol routing choice in situations where a call can be placed using either protocol (for example, with SIP and H.323 protocols).

    0 - Default protocol is used and the user does not choose.

    Supports VVX 500/501, 600/601, and 1500 phones.

    No

    features.cfg

    up.manualProtocolRouting.softKeys

    Display soft keys that control Manual Protocol Routing options.

    1 (Default) - Soft keys are enabled. Use soft keys to choose between the SIP or H.323 protocol.

    0 - Soft keys for protocol routing do not display.

    You can use this parameter with the VVX 500/501, 600/601, and 1500 phones.

    No

    reg-advanced.cfg, h323.cfg

    call.autoAnswer.H323

    This parameter is available for the VVX 500/501, 600/601, and 1500. 0 (default) - Disable auto-answer for H.323 calls.

    1 - Enable auto-answer for H.323 calls.

    No

    sip-interop.cfg

    call.enableOnNotRegistered

    Lync Base Profile – 0 (default)

    Generic Base Profile – 1 (default)

    1 - Users can make calls when the phone is not registered. When set to 1, Polycom VVX 500/501, 600/601, and 1500 business media phones can make calls using the H.323 protocol even though an H.323 gatekeeper is not configured.

    0 - Calls are not permitted without registration.

    Yes

    reg-advanced.cfg, video.cfg

    call.autoAnswer.videoMute

    You can use this parameter for the VVX 500/501, 600/601, and 1500 business media phones.

    0 (default) - Video begins transmitting (video Tx) immediately after a call is auto-answered.

    1 - Video transmission (video Tx) is initially disabled after a call is auto-answered.

    No

    video.cfg

    call.autoRouting.preferredProtocol

    You can use this parameter for the VVX 500/501, 600/601, and 1500 business media phones.

    SIP (default) - Calls are placed via SIP if available or via H.323 if SIP is not available.

    H323 - Calls are placed via H.323 if available, or via SIP if H.323 is not available.

    No

    sip-interop.cfg

    call.autoRouting.preference

    You can use this parameter for the VVX 500/501, 600/601, and 1500 business media phones.

    line - Calls are placed via the first available line, regardless of its protocol capabilities. If the first available line has both SIP and H.323 capabilities, the preferred protocol is used ( call.autoRouting.preferredProtocol ).

    protocol - The first available line with the preferred protocol activated is used, if available. If not available, the first available line is used. Note that auto-routing is used when manual routing selection features ( up.manualProtocolRouting ) are disabled.

    No

    sip-interop.cfg

    reg.x.protocol.H323

    You can use this parameter for the VVX 500/501, 600/601, and 1500.

    0 (default) - H.323 signaling is not enabled for registration x.

    1 - H.323 signaling is enabled for registration x.

    No

    site.cfg

    reg.x.server.H323.y.address

    Address of the H.323 gatekeeper.

    Null (default)

    IP address or hostname

    No

    site.cfg

    reg.x.server.H323.y.port

    Port to be used for H.323 signaling. If set to Null, 1719 (H.323 RAS signaling) is used.

    0 (default)

    0 to 65535

    No

    site.cfg

    reg.x.server.H323.y.expires

    Desired registration period.

    3600

    positive integer

    No

    h323.cfg

    voIpProt.H323.autoGateKeeperDiscovery

    1 (default) - The phone will attempt to discover an H.323 gatekeeper address via the standard multi cast technique, provided that a statically configured gatekeeper address is not available.

    0 - The phone will not send out any gatekeeper discovery messages.

    Yes

    h323.cfg

    voIpProt.H323.blockFacilityOnStartH245

    0 (default) - facility messages when using H.245 are not removed.

    1 - facility messages when using H.245 are removed.

    Yes

    h323.cfg

    voIpProt.H323.dtmfViaSignaling.enabled

    1 (default) - The phone will use the H.323 signaling channel for DTMF key press transmission.

    0 - The phone will not use H.323 signaling channel for DTMF key press transmission.

    Yes

    h323.cfg

    voIpProt.H323.dtmfViaSignaling.H245alphanumericMode

    1 (default) - The phone will support H.245 signaling channel alphanumeric mode DTMF transmission.

    0 - The phone will not support H.245 signaling channel alphanumeric mode DTMF transmission

    Note: If both alphanumeric and signal modes can be used, the phone gives priority to DTMF.

    Yes

    h323.cfg

    voIpProt.H323.dtmfViaSignaling.H245signalMode

    1 (default) - The phone will support H.245 signaling channel signal mode DTMF transmission.

    0 - The phone will not support H.245 signaling channel signal mode DTMF transmission.

    Yes

    h323.cfg

    voIpProt.H323.enable

    0 (default) - The H.323 protocol is not used for call routing, dial plan, DTMF, and URL dialing.

    1 - The H.323 protocol is used for call routing, dial plan, DTMF, and URL dialing.

    Yes

    h323.cfg

    voIpProt.H323.local.port

    Local port for sending and receiving H.323 signaling packets.

    0 - 1720 is used for the local port but is not advertised in the H.323 signaling.

    0 to 65535 - The value is used for the local port and it is advertised in the H.323 signaling.

    Yes

    sip-interop.cfg

    voIpProt.H323.local.RAS.port

    Specifies the local port value for RAS signaling.

    1719 (default)

    1 to 65535

    Yes

    h323.cfg

    voIpProt.server.H323.x.address

    Address of the H.323 gatekeeper. Only one H.323 gatekeeper per phone is supported. If more than one is configured, only the first is used.

    Null (default)

    IP address or hostname

    No

    h323.cfg

    voIpProt.server.H323.x.port

    Port to be used for H.323 signaling. The H.323 gatekeeper RAS signaling uses UDP, while the H.225/245 signaling uses TCP.

    1719 (default)

    0 to 65535

    No

    h323.cfg

    voIpProt.server.H323.x.expires

    Desired registration period.

    3600 (default)

    positive integer.

    No

    site.cfg

    sec.H235.mediaEncryption.enabled

    1 (default) - The H.235 media encryption is enabled and negotiated.

    0 - The H.235 media encryption is disabled.

    Yes

    site.cfg

    sec.H235.mediaEncryption.offer

    0 (default) - The media encryption offer is not initiated with the far-end.

    1 - If the sec.H235.mediaEncryption.enabled is also 1, media encryption negotiations is initiated with the far-end; however, successful negotiations are not a requirement for the call to complete.

    Yes

    site.cfg

    sec.H235.mediaEncryption.require

    0 (default) - The media encryption requirement is not required.

    1 - If the sec.H235.mediaEncryption.enabled is also 1, media encryption negotiations are initiated or completed with the far end, and if negotiations fail, the call is dropped.

    Yes