Chris, A simple script to do so would be: route { forward(192.168.1.1, 5060); } That would forward all packets to 192.168.1.1. However, that's probably not what you want. Packets flow both directions, and if you use record-route you can expect to get loose routed stuff as well. Below is from memory, probably won't work, but, it might spawn some ideas. I think there is some good examples on both iptel.org and onsip.org. -g route { # if already record routed just let it pass if(loose_route()) { if(!t_relay()) { sl_reply_error(); }; break; }; # if not ours, don't mess with it, just move it on it's way. if(!(uri == myself)) { if(!t_relay()) { sl_reply_error(); }; break; }; # if from our gateway then forward to internal UAC (for example) if(src_ip == 192.168.100.1) { record_route(); rewritehostport("192.168.1.1:5060"); if(!t_relay()) { sl_reply_error(); }; break; }; # relay everything else outside rewritehostport("192.168.100.1:5060"); if(!t_relay()) { sl_reply_error(); }; } On 7/6/05, Chris Mason <lists(a)masonc.com> wrote: -- Greg Fausak greg(a)thursday.com