there is indeed a loop going on there after a hold attempt. It seems
you can now reproduce this at will. sipx bridge debug level log would
help pinpoint where the loop is happening.
On 04/24/2012 05:58 PM, Sven Evensen wrote:
We have this call scenario (sipX 4.4)
Ext calls to int A (860)
A transfers to B (864)
B has ring "at same time" C (868)
B has "no repsonse" 25sec
C has "no response" 25 sec, then forward to A
A call to this scenario caused sipxBridge to go crazy and sent
numerous INVITE then 100 Trying to itself. This caused the system to
go to 100% CPU and eventually all calls gave busy.
Please see attached trace.xml
We are having daily 100% CPU issues, most likely with sipxBridge. Any
ideas on how to troubleshoot this is greatly appreciated.
Sven.
--
*Sven Evensen, Operations Consultant*
*OnRelay*
Elizabeth House ? 39 York Road, London SE1 7NQ, UK ? +44 (0) 207 902
8123 ? mailto:[email protected] ? www.onrelay.com
<http://www.onrelay.com/>
This electronic message transmission contains information from
OnRelay, Ltd., that may be confidential or privileged. The information
is intended solely for the recipient and use by any other party is not
authorised. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this
information or any attachment, is prohibited. If you have received
this electronic transmission in error, please notify us immediately by
electronic mail ([email protected] <mailto:[email protected]>) and
delete this message, along with any attachments, from your computer.
Registered in England No 04006093 ¦ Registered Office 1st Floor, 236
Gray's Inn Road, London WC1X 8HB
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
