![]() To enable classification by Proxy Set, configure the IP Group table's 'Classify By Proxy Set' parameter to Enable (see Configuring IP Groups).Ĭlassification using the SIP Contact header is supported only when the header's SIP URI has an IP address (not a DNS hostname).įor IDS, only the source IP address is used (see Configuring IDS Policies).įor TLS Contexts, only the source IP address is used. Only if there is no match, does the device check if the IP address in the SIP Contact header of the incoming SIP dialog matches an IP address in the Proxy Set. Both = The device first checks if the source IP address (ISO Layer 3) of the incoming SIP dialog matches an IP address in the Proxy Set that is associated with the IP Group. The Mediant CE on Azure communicates using internal IP addresses and thus, the Internal Load Balancer doesn't perform SNAT translation and packets typically arrive with the IP address of the active Signaling Component virtual machine, instead of the Load Balancer. This option is useful, for example, when the source IP address is an internal address like when the Mediant CE SBC is deployed in Azure. If a match is found in the Proxy Set, the call is classified to the IP Group. This is only applicable if the header contains a SIP URI that has an IP address (not hostname) in the host part. Contact Header = The device checks if the IP address in the SIP Contact header of the incoming SIP dialog matches an IP address in the Proxy Set that is associated with the IP Group. IP address = (Default) The device checks if the source IP address (ISO Layer 3) of the incoming SIP dialog matches an IP address in the Proxy Set that is associated with the IP Group. The general SIP parameters are described in the table below.Ĭonfigure voip > sip-definition settings > classify-by-proxy-set-modeĭefines which IP address to use for classifying the incoming SIP dialog message to a Server-type IP Group, based on Proxy Set.
0 Comments
Leave a Reply. |