On Mon, 2010-03-15 at 18:26 -0500, Andres Jaramillo wrote: > I just upgrade the SIPX SERVER from 3.10 to 4.0.4 But The AudioCodes > still receiving this kind of messages, now in this form > > > 6d:21h:22m:35s SUBSCRIBE sip:6346...@192.168.0.122 SIP/2.0 > Record-Route: > Via: SIP/2.0/TCP > 192.168.0.120;branch=z9hG4bK-sipXecs-23d1847de02e601950a227e6233094d89246 > Via: SIP/2.0/TCP > 192.168.0.120;branch=z9hG4bK-sipXecs-23ce067a5be67089a6c4c26f1fa6aca6d2a7~41efb91317c490b01dba0712b5e82749 > Via: SIP/2.0/UDP > 192.168.0.120;branch=z9hG4bK-sipXecs-23c91029958c52321db109d93ed584126d95~7573e7cdfaf4501dcca57c7a42c07867 > Via: SIP/2.0/TCP > 192.168.0.84:60584;branch=z9hG4bK-d8754z-d61e5a5f3e30c620-1---d8754z-;rport=64535 > Max-Forwards: 16 > Contact: > To: "Vinos PC MIlagros" > From: "Silvana Quintero";tag=57679b76 > Call-Id: NDM3M2VhNDM0NjIyYmI1MTc3OGI2MzRlYzI4ODc1ZTg. > Cseq: 2 SUBSCRIBE > Subje > > > 6d:21h:22m:35s 120",response="935b7527fc54044349992817b0f636d1",algorithm=MD5 > User-Agent: SMC 3455 release 1014c stamp 46298 > Event: presence > Content-Length: 0 > Date: Mon, 15 Mar 2010 23:04:50 GMT
> The Problem here is that the AudioCodes is filling this memory in some > way , and after I time it drop the calls and show this message > > > 6d:13h:14m:53s ( lgr_freeid)(2211117 ) !! [ERROR] no more free IDs > available > 6d:13h:14m:53s ( sip_stack)(2211118 ) !! [ERROR] new AcSIPDialogAPI can > not be allocated > This suscribe events are receiving by the AudioCodes every 3 to 4 > mins. > > > Anyone know how to disable this kind of messages ? ( reinstall the > softphones ??? maybe ) First of all, I'd check to see if the Audiocodes software is up to date and if they have a fix - that's a pretty serious bug. There's no reason why rejecting a SUBSCRIBE request should be leaking resources. The feature on the SMC phone that is triggering those requests is 'buddy presence' - if you tell the phones not to watch for presence in the address book, it may suppress sending the requests. It may also be possible to prevent the requests being routed to the gateway in the first place, but you have not provided enough information about your configuration to tell. In the example you cited, what is '6346335' ? Is that a user identity on your system? (some soft phone thinks that it is, apparently). Some dial plan rule in your configuration is routing it to the gateway, so I'm guessing that you have a rule that matches any 7 digit number and sends the call to the Audiocodes. You can prevent such a rule from taking effect by making sure that some other rule finds a path for the call first. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
