Christian Rößner <[email protected]> wrote: > So am I right that IPs from SIP providers seems to be the only solution at > the moment?
That would be my best guess - but of course, only for "known" providers. In the day job I've installed a number of on-site PBXs (and we run one ourselves) - some of which have remote users. Good luck pinning those down without a load of management effort - don't forget that you need a means of identifying when to stop treating a destination as privileged. Another approach may be to look at the packets themselves. I've no idea if RTP packets have useful "headers" in them, but VoIP packets are likely to share certain characteristics in terms of size and frequency. So if you see a constant stream of regular size packets *both ways* between two specific IPs then there is a good chance that they are an RTP stream, and if they are small enough then they are likely to be voice. All of this is well outside of my knowledge and experience though. ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees_APR _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
