Well, in SIP, the thing you really have to worry about most is the IP information that is contained within the packet's payload itself, since that is really the deciding factor in call negotiation. Basically what would happen in these nstances is that in Twinkle's twinkle.log file, I'd see packets going from my laptop (192.168.1.44), back to 192.168.1.44 even though my Asterisk I was trying to reach is at 192.168.1.43. For this reason, even though at the Twinkle CLI I'd type call sip:300 at 192.168.1.43 (a test extension I have here), I just get put back at a "twinkle>" prompt with no discernible activity occurring at the console. On Fri, Jan 28, 2011 at 01:33:27PM -0500, Kitty Litter wrote: > I am trying to learn more about the sip protocol and started using > tcpdump. Could you tell me what options you use? It isn't alwalys > clear to me the source and destination of the packets, I use -A and > -t and -c count. > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > -- Igor -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
