Mike, you have hit the nail on the head on all points imho. I am using an Avaya SCS behind an Avaya CM as a conference bridge. I too have noticed a couple of occasions when the one phone (and everything else) I have on the system stops working (idle display, cannot call any number, shows as not registered in SCS), also I cannot connect with a softphone, and the conference bridges stop taking calls. A restart of all services is the only way to get the system running again, (I have not had time to study if re-starting certain services will fix it, as the problem is very sporadic) I have logging on debug and one snapshot, but am not sure if it caught the problem yet.
As a side note I had a four site SCS system under Nortel branding last year that showed similar problems at one site, Nortel was unable to provide answers at the time because the snapshots were "inconclusive". The systems have since been replaced with another solution. These are the reasons I have been following your post, it kind of sounds familiar. My current sipXecs system does not include conferencing so for now I can't reproduce it on sipXecs. To anyone I may have offended with my voracious support of integrated diagnostic tools, I truly am sorry - I am kind of a GUI guy, and love to see things being diagnosed live and real time. I agree that a well timed snapshot should capture this (potential) issue. -------------------------------------------------- From: <m...@grounded.net> Sent: Friday, July 02, 2010 4:04 PM To: "sipx-users" <sipx-users@list.sipfoundry.org> Subject: Re: [sipx-users] All phones expired after conf call > So, if we're back on track, here is the thing. > > The first time I came across having to generate those logs, it didn't > work. Trying to merge logs lead me into another issue of not being able to > even see any logs being created. I searched everywhere for information on > doing this but wasn't able to find anything which lead me to finding a > solution. > > See; > Subject: [sipx-users] Caller ID issue > Date: Tue, 11 May 2010 20:40:05 -0500) > > The last post on that topic was from yourself Dale, telling me to turn up > logging to debug levels which I am pretty sure I had posted to have tried > without success. So, I needed to get past the merging problem so that I > could then generate logs to actually start seeing anything at all. > >> Actually, the *entire* suite of diagnostic tools that Avaya people use >> for >> commercial customers is included in the open-source distribution: sipx- >> snapshot, merge-logs, sipviewer, sipx-response-correlator, etc. Some > > I think some people are only asking if it would be possible to integrate > some of those things into the system itself, so that there aren't so many > steps involved in trouble shooting. The other poster has a valid point, > when a system goes down, you don't always think about generating logs as > much as you NEED to get the darn thing back up and running. That is the > priority. > >> If you know of any way that one might build an "expert system" that could >> do this diagnosis directly at the request of the administrator, rather >> than > > I am willing to bet if users mulled it around in a positive way that some > good ideas could be generated and perhaps even turned into solutions that > would help the overall product. Just need to let people voice their > thoughts, not everyone is a full time sipx expert guru that does only that > for a living. > > Mike > > > _______________________________________________ > 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/ _______________________________________________ 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/
