From: "Alfred E. Heggestad" <[EMAIL PROTECTED]> [EMAIL PROTECTED] wrote: > From: "Alfred E. Heggestad" <[EMAIL PROTECTED]> > > This also means that any incoming datagrams must be sent from the > same peer. > > What if the incoming datagrams are not sent from the same peer? RFC > 3261 permits the peer to send from a different socket or even IP > address.
ok, so the SIP socket cannot be connected, meaning that I have to use raw sockets to get ICMP destination unreachable message, which means that my application must run as root? I'm not an expert in these matters, and of course, it depends on your stack. But some stacks give a similar effect even with unconnected sockets -- the second or third time a packet is sent to a particular destination, if the kernel received a Destination Unreachable for that destination in the recent past, the stack will return a Destination Unreachable error for the attempted send. but for STUN and RTP (symmetric) a connected UDP socket should still work I guess? That makes much more sense, as a device is likely to participate in only a few media streams, and send many packets to each destination, whereas a SIP signalling stack will send few packets to each of many destinations. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
