[cisco-voip] RTMT??? or some other way to monitor a phone

[Scott Voll]

I was really hoping not to pull SDL traces (more work) and I was hoping
just to look at a small segment of phones not everything.

Guess that answers my question.

Scott



On Thu, May 7, 2015 at 5:19 PM, Brian Meade <bmeade90 at vt.edu> wrote:

> Using the Syslog Viewer in RTMT, open the AlternateSyslog for the primary
> subscriber the phones are registered to.  That will show all phone
> registrations/unregistrations.
>
> On Thu, May 7, 2015 at 5:42 PM, Scott Voll <svoll.voip at gmail.com> wrote:
>
>> we have 8861 phones that are just below an AP that are registering and
>> unregistering (but working well enough that we have not moved them back to
>> wired) so we are trying to monitor how much it's happening.  Already have a
>> TAC case open on the wireless side.
>>
>> Scott
>>
>>
>> On Thu, May 7, 2015 at 2:38 PM, Ryan Huff <ryanhuff at outlook.com> wrote:
>>
>>> Might be easier to start the other way around.
>>>
>>> What is actually wrong?
>>>
>>> RTMT does work with registered phones, and presumably,  your wireless
>>> phones are registered?
>>>
>>> Are the wireless phones not registering to call manager?
>>>
>>> Thanks,
>>>
>>> Ryan
>>>
>>>
>>> -------- Original Message --------
>>> From: Scott Voll <svoll.voip at gmail.com>
>>> Sent: Thursday, May 7, 2015 05:34 PM
>>> To: cisco-voip at puck.nether.net
>>> Subject: [cisco-voip] RTMT??? or some other way to monitor a phone
>>>
>>> We are troubleshooting a wireless deployment of 8861 phones.
>>>
>>> is there any way to monitor just a phone / phone model / device pool /
>>> etc so I can just see what I'm looking for?
>>>
>>> Looks like RTMT is just all registered phones.
>>>
>>> TIA
>>>
>>> Scott
>>>
>>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150508/c4d455d8/attachment.html>