We’ve been consistently getting an informational event in our Director’s logs from TMS over the past few weeks and until now, I wasn’t sure where it was coming from. Finally got to the bottom of it the other day though, with a bit of help from a colleague. It seems that a mis-configured SIP device was probably the issue.
There are actually two events, both ID 246, but subtly different:
The Telephony Management Server has logged an informational debug message. The debug message contents are:
.\NccMsgZin.cpp(1470) : Assertion failed: !”SIPReg: Error sending SIP Register”The Telephony Management Server has logged an informational debug message. The debug message contents are:
.\NccMsgZin.cpp(1460) : Assertion failed: !”SIPReg: Error sending SIP Register”
I managed to repoduce this in two ways. We have Shoretel 12 CR3 (build 17.10.1730.0) here and a Shoretel Mobility Router running 4.5. What was causing these messages to appear every two minutes was a user configured on the SMR that didn’t exist in the Director user database. So the SMR must have been trying to register on the user’s behalf, but there was no such account. This was happening every two minutes. Disable the user, and the error messages stop appearing.
I also noticed this when configuring a Pancode SIP doorphone onto the system. I hadn’t set the user’s SIP password in Director correctly – as a result, I was getting about 10 of these messages every minute as the doorphone tried to register with the SIP proxy. Once I got the password set correctly, all the errors stopped occurring.
It does seem a shame that this is not being reported in more plain english – I may well log it as an improvement request on the Shoretel suggestions site!
