mcbridea replied on Tue, Jan 20 2009 12:48 PM

rated by 0 users

Hi Art,

This is an interesting use case. I don't have very many people asking for this type of flexibility but I can see it would be very useful. I'll add it to the roadmap but no commitment to dates or releases at this point.

Andy

Network_Guru replied on Thu, Feb 5 2009 9:55 AM

rated by 0 users

Further to this, I'd like to note an issue with the MOS score charts.

Looking at this chart, there are 2 things wrong:

1) As noted in other threads, 95th percentile is not an average, and this word should not appear below this chart
(I noticed this is fixed in NPM charts, but not in the VoIP monitor module)

2) 95th Percentile for MOS scores is meaningless. A meaningful score would be a 5th percentile.
How low did the MOS value get?
This is what VoIP degradation is based on.

Johnvoip replied on Wed, Jul 8 2009 5:06 AM

rated by 0 users

VoipSipSdk

I am now looking for voip solutions. And found information about Voip sdk.
According to their website www.voipsipsdk.com
Voip sdk is based on IETF standards (SIP, STUN, etc.), so it should be compatible with other standard based products such as Asterisk, OpenSER other.

They have all features I need:
# Dynamically loadable codecs
# Registrar support
# Play wav files into conversation
# Record conversation into file
# Hold/Retrieve call
# Forward Call (Blind Call Transfer)
# Transfer Call (Attended Transfer)
# Mute Sound
# VPN support
# Noise reduction
# Auto gain
# Jitter buffer parameters
# Samples on Delphi, C#, VB, VB.NET, C++ 2005, C++ 6.0, HTML (SIP ActiveX)
# Windowless samples on C++ and .NET
# DTMF
# Adaptive silence detection
# Adaptive jitter buffer
# STUN support
# Comes as ActiveX control

But before I will download the evaluation version I would like to hear other people experience.

bschurr replied on Fri, Nov 20 2009 5:20 PM

rated by 0 users

I just loaded a trial version of IP SLA Manager in our lab and am trying to collect the data from our shadow router. We have the same type of architecture with shadow routers located at our node locations. Currently we send the data to another monitoring device for display, but I have not been able to get it to display in Orion.

I was under the impression that I just need to pull SNMP and collect the data I needed from the MIB, but I am not seeing any of the ip sla monitor sessions showing up as resources. Can you shed some light on the process of adding a shadow router. Do I need to have RW capabilities? Other that UDP 161 are there any ports that need to be enabled through a firewall?

chris.smouse replied on Mon, Nov 23 2009 12:58 PM

rated by 0 users

Hi bschurr -

You will need RW capabilities on the shadow router if you plan to create IPSLA operations via SNMP from IPSLA Manager.

bschurr:

but I am not seeing any of the ip sla monitor sessions showing up as resources.

Not sure what you mean here.  Are you saying you have created IPSLA operations on your shadow router and they are not reporting any statistics?

If you can provide us more specifics on what you're trying to accomplish, that would help.  Is your shadow router on the same subnet as your regular routers, and can your Orion server access the shadow router?

bschurr replied on Mon, Nov 23 2009 1:32 PM

rated by 0 users

The shadow router has allready been configred via CLI to perform the IPSLA operations. The stats are then collected by another monitoring system (VitalSuite). I see in the configuration on the Shadow router that there is an owner field that has an entry for a resoure on Vital Suite. I was wondering if there is something I would need to put in this field that would pertain to Orion?

This is a sample of one of the operations configured on the shadow router.

ip sla monitor 404
 type pathJitter dest-ipaddr 172.19.4.4 num-packets 50
 owner VNETDISC:Seattle-CPE
 tag SLA Monitor Range for pathJitter = 401 - 499
 frequency 120

I have the shadow router in the Orion lab as an SNMP RO device right now. When I list the resources I get all of the interface data, but don't see any of the IPSLA monitoring info.

chris.smouse replied on Mon, Nov 23 2009 4:28 PM

rated by 0 users

Thanks for this additional info.  Since the operations have been set up by CLI, you can use IPSLA Manager's "Monitor existing operations" option in the Operation Wizard to monitor the existing operations.

1.  Make sure your IPSLA nodes are added to IPSLA Manager.  In this case, you won't need read/write since the operation(s) already exist on the device.

2.  Create a new IPSLA Operation, selecting the "Monitor existing operations" option.

When monitoring the existing operation, you will be prompted to enter the operation number toward the end of the Operation Wizard.  To monitor the operation in your example, you would enter "404" as the operation number.

macnugetz replied on Mon, Nov 23 2009 4:29 PM

rated by 0 users

bschurr-

You want to monitor an existing operation. chris.smouse explains how to do this here (I've also pasted it below).

Once you have created the IPSLA operation manually on the router, make a note of the operation number.

Then, go through the Add Operations wizard in IPSLA Manager.  Instead of creating a new operation, you need to choose the "monitor existing" option.

Toward the end of the wizard, you will have the opportunity to enter the operation number for the custom operation.

-Craig

bschurr replied on Tue, Nov 24 2009 10:36 AM

rated by 0 users

The problem I have is that I don't have the ability to discover the endpoints in NPM. I am needing to put the site in by ip address, or be able to continue with just specifying a source node. I see by the attached threads that this is something in the works. Do you have a date that I can pass on. I am trying to set this up a s trial for customer that is in the market for VOIP  and IPSLA monitoring tools and this could be a deal breaker.

http://thwack.com/forums/t/20616.aspx

http://thwack.com/forums/p/20038/82589.aspx#82589

Chandru replied on Fri, Nov 27 2009 10:44 AM

rated by 0 users

Hi Guys,

Is there a way that we can get alert suppression and dependencies working

As we would receive node down alert, interface alert, IP SLA alerts too many alerts and offcourse reboot alert

Is there any way we could combine all this into a single alert and suppress all other relevant alerts

I think this needs to be considered as a high priority feature as all the applications are integrated with each other why not we have this feature to suppress alerts

if any one has done this already can you share

We have NPM, IP SLA and we get alerts for everything and i am currently looking at the best way of suppressing this alerts when a node reboots

I am also looking if there is a way that if power to a site is down and all nodes reboot can that be sent as a single alerts rather than 50 alerts if we are monitoring 50 devices

Solarwinds guys can you please help?

Thanks

Chandru

derhally replied on Mon, Nov 30 2009 9:28 AM

rated by 0 users

NinjaNerd56 :

From what you described, I'm assuming that you created the operations through IP SLA.  IP SLAM should try to recreate those operations.   Since it did not I would open a support ticket so that the developers can look into this issue.

derhally replied on Mon, Nov 30 2009 9:38 AM

rated by 0 users

Chandru:

We currently don't expose the target node's status for alerts which would give you to suppress alerts the way you wish.  You should file a ticket with support and request it as a feature so you can track it.