Does SER have support for preserving the DSCP markings of (incoming) SIP messages it processes before sending them out? Or is this something one would need to change the SER source code for? I searched in the archives but could not find anything relevant.
Regards, -Ravi.
Hi!
Ravindranath Gummadidala wrote:
Does SER have support for preserving the DSCP markings of (incoming) SIP messages it processes before sending them out?
No.
Or is this something one would need to change the SER source code for? I searched in the archives but could not find anything relevant.
You could enhance the structures in ip_addr.h to store the information received. The way SER uses UDP sockets would force you to do setsockopt() quite often, though. SER already allows you to set a resonable global default (i.e. tos=104) in ser.cfg which is used for all outbound messages.
Just out of curiosity: What's your application? Do you need different TOS values on different 'routes'?
Hendrik
Moin!
On Fri, Jun 01, 2007 at 10:38:18AM +0200, Hendrik Scholz wrote:
You could enhance the structures in ip_addr.h to store the information received. The way SER uses UDP sockets would force you to do setsockopt() quite often, though.
Also, as the UDP sockets are shared between all processes, you would have to obtain a lock before doing the setsockopt() and sendto() calls.
I thought that it might be possible to do it with a single system call using sendmsg() and passing the TOS value as ancillary data, but I just tested this, and unfortunately it doesn't seem to work.
Note also that the IP_RECVTOS socket option, which is used to obtain the TOS value of received packets, seems to be available only on Linux.
Regards, Jan
-
Hendrik Scholz -
Jan Andres -
Ravindranath Gummadidala