Technical data

ServerIron ADX Advanced Server Load Balancing Guide 27
53-1002435-03
SIP SLB command reference
1
Debugging UDP processes
Syntax: show sip debug udp-process
Debugging SIP packet traces
The show sip debug packet-trace command shows the packets with the IP address of either
<src-or-dest-IP-1> or <src-or-dest-IP-2>. The output displays packet processing starting from
parsing to forwarding. The command is very useful in debugging; however, it only displays in the BP
console not on rconsole.
Syntax: show sip debug packet-trace <src-or-dest-IP-1> <src-or-dest-IP-2>
The following example is a display of "INVITE" packet processing shown on a BP console.
SIP SLB command reference
This section describes the syntax and usage for each SIP Server Load Balancing command in the
real server configuration mode and the virtual server configuration mode.
Real server configuration mode
Use the port sip command in the real server or virtual server configuration mode to configure a
proxy, redirect, registrar, or registrar-proxy server. These commands are issued from the real server
configuration.
ServerIronADX# show sip debug udp-process
SIP UDP Process Counters:
UDP ERR :0 UDP NO HEADER :0
UDP UNKNOWN PKT :0 UDP PKT TO MP :0
UDP FWD DROP :55 UDP REV DROP :2
UDP NO ACTION :0
ServerIronADX4/2 # show sip debug packet-trace 172.28.8.67 172.28.8.100
4/2 #
->Start processing Incoming Flow [172.28.8.67:3798->172.28.8.100:5060] Data len
[1460]...
Start SIP Parsing for chain len [1460]...
SIP header parsing for flow COMPLETED with sip header - orig chain len [1460]
SIP packet header dump:
Packet type: INVITE
URI: sip:service@172.28.8.100:5060 version: SIP/2.0 response code: 0
parse completed: 1 num pkts processed: 1 method: INVITE
VIA header: SIP/2.0/TCP 172.28.8.67:5060;branch=z9hG4bKnashds8
Max forward: 70
Call ID: [e-mail]
Cseq: 1 INVITE
Top branch id: z9hG4bKnashds8
Top Sent By: 172.28.8.67 Top Sent By Port: 5060
In sip_process_incoming_frontend_request...
Current transaction: branch [z9hG4bKnashds8] client[172.28.8.67]
Forwarding request from flow [172.28.8.67:3798->172.28.8.100:5060] to Server
[172.28.8.155:5060->172.28.8.67:3798]