I dont have a whole lot of info, but the customer reported that the SIP trunk was blocked and a restart of SIP trunking on our side resolved it. And this is supposedly 3-4 time it happens.
What I do see in the attached sipxbridge.log is a semaphore timeout at 2012-07-30T09:05:14.779000Z followed by a few minutes of non stop timeouts. At 2012-07-30T09:38:34.617000Z there is no more logging until the customer does the service restart two hours later. Even more worrying is that there were no alarms generated. Btw, sipx 4.4. Attachment here http://dl.dropbox.com/u/23533328/sipxbridge.log.zip Sven -- *Sven Evensen, Operations Consultant* *OnRelay* Elizabeth House │ 39 York Road, London SE1 7NQ, UK │ +44 (0) 207 902 8123 │ mailto:sven.even...@onrelay.com <sven.even...@onrelay.com> │ 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 (i...@onrelay.com) 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 sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
