Gavin Henry wrote: > On 18 August 2010 13:47, Gavin Henry <[email protected]> wrote: > >> On 18 August 2010 10:23, Gavin Henry <[email protected]> wrote: >> >>> I was thinking: >>> >>> if (is_method("OPTIONS|INFO")) >>> { >>> sl_send_reply("501", "Method $rm not implemented"); >>> exit; >>> }; >>> >>> >> I think I'll add in above. Also, I think I've figured it out. The logs >> show these broken dialog inserts. I've just got a SIP trace of when it >> starts failing and Service Full is being returned. I think as these >> dialogs don't get closed they are sitting as open calls and when we >> hit our LB limit it gets full and a restart clears the tables. >> >> Need to check where the ongoing calls are saved so I can see what >> we're at now. All frpm a broken OPTIONS message! >> > > Found it! Every 30 seconds we get this broken SIP OPTIONS message and > sure enough, as our calls get open and closed it's sneeking up the > load. I can see it via: > > opensipsctl fifo lb_list > > Can I block OPTIONS like above? >
Again, depends on what these OPTIONS are used for.....if they are for checking the call sanity, you should relay it (or answer with 200 OK). If just NAT pings, send back whatever you want. Regards, Bogdan -- Bogdan-Andrei Iancu OpenSIPS Bootcamp 20 - 24 September 2010, Frankfurt, Germany www.voice-system.ro _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
