Comments
-
Any idea as to when the VNQM product house are going to step it up a little? Seems over the years that VNQM has moved from the back seat to the trunk. Feature requests are near no existent and some simple common sense issues are never fixed. Recent upgrades too have destroyed our CDR platform yet “Dev Team” never come to…
-
Just the ability for VNQM to monitor SIP-UA registration would be great, Would have thought this would be a default operation to monitor carrier SIP status.
-
Totally agree – facing the exact same issue now. Surely there must be a DB edit to tell SW it is a VoIP gateway. I have a case open however I don’t think SW will provide a work around and agree, this is not a Cisco issue either.
-
Thanks, may I ask the menu to find it? Does not seem to be found in the logical places some would expect it to be. Cheers!
-
Yep - I too am missing this. Was working well until I upgraded our Orion instance due to recent security issue this week and now I cant monitor the realtime logs etc.
-
Thanks mate - but yes, see that one before but did not resolve anything. Cheers!
-
Not sure as the link you posted goes to a "Not Found" landing page mate. Cheers!
-
Thanks mate - yes any help much appreciated as my head is getting sore from the brick wall Cheers!
-
Yep - as before, have followed all available articles. To re-cap, I have set them all up with AXL access (above and beyond the min requirements) and CDR is also flowing in - no issues in that space. It is just when you click on one of the call managers, non of the SIP trunks look like they are being polled. We have 123 SIP…
-
Yes - would say by now 50 times over... Attached is the Call Manager status which clearly shows everything enabled. AXL credentials also have more then the recommended. Seems to be a common question but no real resolve posted.
-
Try log a support case for them to assist. In my instance is was some "null value" in the SQL that was causing the issue. The Developer provided a Buddy Drop to fix the issue. Long winded proccess but got there in the end
-
Hello, yes, have managed to do that but the issue is that it does not show a "total" for all SIP dial peers. So for example, if we have 4 sip trunks, and let’s say they are currently have 5 calls each established. Opposed to seeing 4 individual graph lines showing 5 calls each, but maybe a way to add a line for total (e.g.…