Re: PGW SIP errors

pax_2111 · ‎11-22-2009

Hi all,

I am receiving the following error in platfrom. log in one of our PGW 2200:

Sat Nov 21 19:49:59:421 2009 GMT | sip-1 (PID 5639) <Error>
The destination ipaddr is invalid, drop this packet!

I set the logging level for sip-1 to trace but couldn't see any further info.

Has anyone an idea how I can see the destination IP at least?

Will setting debug level help?

rgrds

virverma · ‎11-22-2009

These messages correspond to a situation where PGW cannot
do a reverse name resolution (PTR RR DNS query) on some IP addresses
coming in a request from the proxy

You can use siptool to check which
DNS name lookup failure, and check which DNS name is cached in SIP IOCC

This should help!

pax_2111 · ‎11-22-2009

thanks, that was really helpful.

Do you happen to know if there is any docs for siptool? I can't seem to find it in the PGW maintenance guide.

virverma · ‎11-22-2009

not sure if any but you can launch siptool

/opt/CiscoMGC/etc/cust_specific/current >>siptool

type h for help

this should help!

pax_2111 · ‎11-22-2009

I ran the siptool as is and saw the help, but didn't get any meaningful output.

Can you pls be clearer about the command line: /opt/CiscoMGC/etc/cust_specific/current >>siptool .

The command line looks strange for me as /current is a directory and is being redirected to a binary?

Anyhow, it looks a pretty useful tool, but it's a shame that there is not a few lines about it in Cisco docs.

virverma · ‎11-23-2009

There might be some information available,

but if you are working in a firm which has PGW deployed you can contact the account team or TAC to get meaningful information

Thanks!

donaliforb · ‎12-21-2009

Hi Pax,

Here is a short overview on using SIPtool. There is no official documentation describing this nice little tool so I put this together.. good luck. If you need any further help with it just let me know.

Rgds

Donal Whooley

IFORB GmbH, PGW2200 & BTS10200 Networking
Skype/Yahoo/AOL/Gtalk: donalwho

Google Wave: donalwho@googlewave.com

www.iforb.com

1: Set debug mode

This allows the user to set or clear specific debug flags. If 'D' is entered without any parameters, it will display the current state of all flags.

syntax:D [flag] ["on"/"off"]

flag = debug (IOCC debug)

print (debug print statements)

sip (SIP Messages to/from IP)

eng (Engine Messages to from engine)

dns (DNS Messages)

all (all Messages)

example:

siptool@test-system0> d sip on

Operation Successful

Dflags

IOCC debug = off

Print = off

Sip Msgs = on

Engine Msgs = off

Dns Msgs = on

ICMP Msgs = off

2: Cache information

This will display the contents of the DNS cache.. If 'CI' is entered without any parameters, it will display the first 10 cache entries starting from position 0.

3. CC

This will clear the contents of the DNS cache. This command takes no parameters.

syntax:CC

4: Filter Configuration

This will set the configurations of the filters used to determine what information is put into the trace buffer by the IOCC. The filter configurations resides on the IOCC. Upon startup, the siptool will read the current IOCC filter settings. If 'FC' is entered without any parameters, it will display the current state of all the filters. If 'FC' is entered with just a filter number, that filter configuration is cleared and the filter set inactive.

syntax:FC [#] [type] [string]

# = filter number 0 thru 3

type = c | s | i

string = string to match

where c = call ID, s = subscriber and i = IP addr

example:

siptool@test-system0> fc 0 c 123456

Operation Successful

siptool@test-system0> fc

Getting filter configuration... Operation Successful

Current Filter Setting

Filter Sequence: None

filter 0 (active) - Call ID on '123456'

filter 1 (active) - Subscriber on 'Micky'

filter 2 (inactive)

filter 3 (inactive)

5. Filter Sequence

This will set the sequence of the filters used to determine what information is put into the trace buffer by the IOCC. The filter sequence resides on the IOCC. Upon startup, the siptool will read the current IOCC filter sequence. Upto 4 filters can be specified within a sequence. The order of evaluation is left to right.

syntax:FS F# op F# [op F# ....]

# = filter number 0 thru 3

op = '&' (logically AND) or '|' (logically OR)

example:

siptool@test-system0> fs f1 & f2 | f0

Getting filter sequence... Operation Successful

Current Filter Setting

Filter Sequence: F0 & F1

filter 0 (active) - Call ID on '123456'

filter 1 (active) - Subscriber on 'Micky'

filter 2 (inactive)

filter 3 (inactive)

6: TA

This will display any new trace entries, starting at the end of the trace. This command takes no parameters