> That's fine, but I instructed you to *note down the extension of an > affected phone*, and you did not do that. The importance of that step may > not be obvious, but I've learned the hard way that when trying to fix a
I fully agree, and I need to be more detailed when I have problems with sipx. > the merge-logs command, and since you didn't note down a failing extension, > you were stuck making a guess at how to run merge-logs. What happened is that I was looking for the incoming number which I didn't realize isn't an extension, it is an 800 number forwarded to another number on our PRI which is handled by sipx. Pressure has a way of causing mistakes to be made but when it turns as ugly as it did, that didn't help anything either. Being able to think clearly and work through the process makes things come together. I'm still trying different settings on one of those servers to see if I can get the clock problem solved and dealing with new problems which occurred over the weekend. I believe that we found the problem for this thread, which ultimately ended up being the clock. I don't know if you would like me to still use the old system to learn about getting the output etc, or keep your notes and follow them the next time that something does go haywire. Mike
_______________________________________________ sipx-users mailing list [email protected] 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/
