ADC NITRO APIs

lsnsipalgcall_controlchannel_binding

Binding object showing the controlchannel that can be bound to lsnsipalgcall.

Properties

(click to see Operations )

Name Data Type Permissions Description
callid <String> Read-write Call ID for the SIP call.
channelip <String> Read-write IP address of the channel.
channelnatip <String> Read-only Natted IP address of the channel.
channelport <Integer> Read-only port for the channel.
channelflags <Double> Read-only Flags for the call entry.
channeltimeout <Double> Read-only Timeout for the channel.
channelnatport <Integer> Read-only Natted port for the channel.
channelprotocol <String> Read-only Channel transport protocol.

Possible values = HTTP, FTP, TCP, UDP, SSL, SSL_BRIDGE, SSL_TCP, NNTP, RPCSVR, DNS, ADNS, SNMP, RTSP, DHCPRA, ANY, SIP_UDP, SIP_TCP, SIP_SSL, DNS_TCP, ADNS_TCP, HTTPSVR, HTTPCLIENT, NAT, HA, AAA, SINCTCP, VPN AFTP, MONITORS, SSLVPN UDP, SINCUDP, RIP, UDP CLNT, SASP, RPCCLNTS, ROUTE, AUDIT, STA HTTP, STA SSL, DNS RESOLVE, RDP, MYSQL, MSSQL, DIAMETER, SSL_DIAMETER, TFTP, ORACLE, ICA, RADIUS, RADIUSListener, SMPP, PPTP, GRE, SYSLOGTCP, SYSLOGUDP, FIX, SSL_FIX, QUIC, TFTP_DATA, USER_TCP, USER_SSL_TCP, MONGO, MONGO_TLS, MQTT, MQTT_TLS, QUIC_BRIDGE, HTTP_QUIC, CT_TCP, CT_UDP
__count <Double> Read-only count parameter

Operations

(click to see Properties )

  • GET
  • GET (ALL)
  • COUNT

Some options that you can use for each operations:

  • Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the 'warning' query parameter as 'yes'. For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

    http:// <netscaler-ip-address> /nitro/v1/config/login?warning=yes

    If any, the warnings are displayed in the response payload with the HTTP code '209 X-NITRO-WARNING'.

  • Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:

    X-NITRO-USER: <username>

    X-NITRO-PASS: <password>

    Note: In such cases, make sure that the request header DOES not include the following:

    Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

*Note: * Mandatory parameters are marked in red and placeholder content is marked in green

get

URL: http:// <netscaler-ip-address> /nitro/v1/config/lsnsipalgcall_controlchannel_binding/ callid_value<String> Query-parameters: filter http:// <netscaler-ip-address> /nitro/v1/config/lsnsipalgcall_controlchannel_binding/ callid_value<String> ? filter=property-name1:property-value1,property-name2:property-value2

Use this query-parameter to get the filtered set of lsnsipalgcall_controlchannel_binding resources configured on NetScaler.Filtering can be done on any of the properties of the resource.

pagination http:// <netscaler-ip-address> /nitro/v1/config/lsnsipalgcall_controlchannel_binding/ callid_value<String> ? pagesize=#no;pageno=#no

Use this query-parameter to get the lsnsipalgcall_controlchannel_binding resources in chunks.

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Accept:application/json

Response: HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Header:

Content-Type:application/json

Response Payload:

{  "lsnsipalgcall_controlchannel_binding": [ {
"callid":<String_value>,
"channelip":<String_value>,
"channelnatip":<String_value>,
"channelport":<Integer_value>,
"channelflags":<Double_value>,
"channeltimeout":<Double_value>,
"channelnatport":<Integer_value>,
"channelprotocol":<String_value>
}]}

<!--NeedCopy-->

get (all)

URL: http:// <netscaler-ip-address> /nitro/v1/config/lsnsipalgcall_controlchannel_binding HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Accept:application/json

Query-parameters: bulkbindings http:// <netscaler-ip-address> /nitro/v1/config/lsnsipalgcall_controlchannel_binding? bulkbindings=yes

NITRO allows you to fetch bindings in bulk.

Note: get (all) method can be used only in conjuction with bulkbindings query parameter.

Response: HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Header:

Content-Type:application/json

Response Payload:

{  "lsnsipalgcall_controlchannel_binding": [ {
"callid":<String_value>,
"channelip":<String_value>,
"channelnatip":<String_value>,
"channelport":<Integer_value>,
"channelflags":<Double_value>,
"channeltimeout":<Double_value>,
"channelnatport":<Integer_value>,
"channelprotocol":<String_value>
}]}

<!--NeedCopy-->

count

URL: http:// <netscaler-ip-address> /nitro/v1/config/lsnsipalgcall_controlchannel_binding/ callid_value<String> ? count=yes HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Accept:application/json

Response: HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Header:

Content-Type:application/json

Response Payload:

{"lsnsipalgcall_controlchannel_binding": [ { "__count": "#no"} ] }

<!--NeedCopy-->
lsnsipalgcall_controlchannel_binding