RE: [SA-list] Creating UDP Protocol for SIP

[Dirk Bulinckx]

The problem with this was that the way SA worked it just couldn't work. The UDP definition screen made you think it could work.   With receiving port=same port we expect to get data back on the same client port. Example:     client sends via port 1046 to server on port 5060 we expect to get data back on the client on port 1046   In the latest beta (4.0.1560) we did an update in order to cope with this issue:     receving port=same port (client) -> see above     receving port=+1 -> we expect to get data back on the client on server_port +1 (in the example on 5061)     receving port=-1 -> we expect to get data back on the client on server_port -1 (in the example on 5059)     (those 3 were already within the product)       receving port=same port (server) -> we expect to get data back on the client on server_port (in the example on 5060)     (that's new)   As always the beta can be found on http://beta.woodstone.nu     Dirk.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Wasik Sent: Monday, December 29, 2003 4:29 PM To: [EMAIL PROTECTED] Subject: [SA-list] Creating UDP Protocol for SIP Hi all,   I have used SA to create a custom UDP protocol check for SIP (An IP telephony protocol). I am able to send the packet to the SIP device to be monitored and that device responds as expected. The UDP protocol check I created is set to expect the reply on UDP port 5060 and that is where the monitored device is replying to. (I'm using Ethereal to monitor this.)   However SA does not seem to be listening for the reply or at least not on that port. I used "netstat -an" on Windows XP to check this.   Any suggestions?   Thanks,   Paul