Um, try those two phones with 3.1.3.
On 5/27/10, Melcon Moraes <[email protected]> wrote: > I have upgraded the system to 4.0.4-017289 on CentOS. > > However, the issue still happens. It seems to be related to a directed > callpickup that fails. > > Is there some kind of conflict with Call Forwarding and Direct Pickup? Is > there any problem of using both? > > Attached, the trace files. > > User 6616 receives a call from the outside world; then user 6620 tries to > pick it up by dialing *786616, which fails and triggers the issue. > > In some cases, like this one, no harm was done. In some other cases, the > loop does not end and the sipXproxy is dragged down to its knees, stop > responding to any new request. > > All phones are polycoms IP330 with firmware 3.1.2.0392 > > I can provide the snapshot too. > > Thanks in advance. > MM > > On Thu, May 13, 2010 at 19:15, Melcon Moraes <[email protected]> wrote: > >> Well, I am planning an upgrade to 4.0.4 and then check if this will >> keep happening. I know that 4.0.4 won't cause huge impact >> on my environment. >> >> BTW, I have proxy and registrar log level set to NOTICE. Should I >> raise another component to that level as well? >> >> - >> MM >> >> >> On Thu, May 13, 2010 at 18:08, Tony Graziano >> <[email protected]> wrote: >> > Whike that's odd, 4.02 is "old". At the same time I'm not suggesting >> > you update to 4.0.4 or 4.2 unless You are sure the changes won't >> > affect your environment. >> > >> > On 5/13/10, Melcon Moraes <[email protected]> wrote: >> >> Hi, >> >> >> >> I'm getting sometimes the following WARNING in sipXproxy.log: >> >> >> >> "2010-05-13T13:51:33.342632Z":139712:SIP:WARNING:egvoip.asnet.pt: >> SipClientTcp-18:B6568B90:SipXProxy:"SipTransaction::recurseChildren >> >> loop detected on call 's-5505f8f7d4a5dfa0-10' 3 hops ago had same >> >> contacts" >> >> >> >> What would be causing this? I notice last week some relation between >> >> this loop messages and another one: >> >> >> >> "2010-05-05T16:12:16.786001Z":6754:SIP:CRIT:egvoip.asnet.br: >> SipClientTcp-22:B5DFFB90:SipXProxy:"SipUserAgent::queueMessageToInterestedObservers >> >> send failed with status 12 (numMsgs = 2000, maxMsgs = 2000)" >> >> >> >> At this point, top showed sipxproxy process consuming all the %CPU and >> >> all the phone registrations are lost. I can provide a snapshot for >> >> the siptrace in >> >> http://www.voixtel.com.br/snapshots/sipXproxy-loop_detected.zip and >> >> one for the last week too. >> >> >> >> By restarting the SIPXProxy, things wen back to normal. >> >> >> >> This is sipxecs-4.0.2-016420. >> >> >> >> Thanks in advance. >> >> >> >> - >> >> MM >> >> _______________________________________________ >> >> sipx-dev mailing list [email protected] >> >> List Archive: http://list.sipfoundry.org/archive/sipx-dev >> >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev >> >> sipXecs IP PBX -- http://www.sipfoundry.org/ >> > >> > -- >> > Sent from my mobile device >> > >> > ====================== >> > Tony Graziano, Manager >> > Telephone: 434.984.8430 >> > sip: [email protected] >> > Fax: 434.984.8431 >> > >> > Email: [email protected] >> > >> > LAN/Telephony/Security and Control Systems Helpdesk: >> > Telephone: 434.984.8426 >> > sip: [email protected] >> > Fax: 434.984.8427 >> > >> > Helpdesk Contract Customers: >> > http://www.myitdepartment.net/gethelp/ >> > >> > Why do mathematicians always confuse Halloween and Christmas? >> > Because 31 Oct = 25 Dec. >> > >> > -- Sent from my mobile device ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
