Oh yes. Especially those that break by just looking at them.
[image1.jpeg]
-sent from mobile device-
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G
2W1
519-824-4120
Do you like dongles?
On Fri, Jul 27, 2018 at 3:40 PM Lelio Fulgenzi wrote:
>
> We're looking at ordering a new conference phone... people have complained
> about the two pieces the 8831 has for simple operations so I'm looking at
> the 7832 or 8832.
>
> Looking through the 8832 datasheet, I am
We're looking at ordering a new conference phone... people have complained
about the two pieces the 8831 has for simple operations so I'm looking at the
7832 or 8832.
Looking through the 8832 datasheet, I am a bit confused about the power
injector options. According to the CCW estimator tool,
pull from as many of these
environments are quite large.
Is there any other way to get this info quickly? Thoughts.
Sincerely,
Ryan Burtch
-- next part --
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/2018072
Ryan,
Here is a sample query for that gets you half way there to make it easier to
troubleshoot.
select P.EnterpriseName, T.PeripheralID, *
FROM lab_hds.dbo.t_Termination_Call_Detail T
LEFT JOIN lab_awdb.dbo.Peripheral P ON P.PeripheralID = T.PeripheralID
You can work on that query to get more
Ryan ,
you will still be able to know the ip address of the peripheral via
reg-edit of respective peripherals.
Regards
Manjunath
On Fri, Jul 27, 2018 at 4:30 PM, Ryan Burtch wrote:
> I work in Managed Services. I have to get into different customer
> environments when issues happen. Many
I work in Managed Services. I have to get into different customer
environments when issues happen. Many times, I'm researching a dropped call
or something like that via the AW/HDS.
I see the calls come into RCD/TCD via some Routing Client '5001, 5002,
etc', but I need a way to correlate these
