What we are working on post VoIP & Network QM 4.0

We processing all the feedback you guys provided us and our engineering teams are already working on couple of improvements:

PRI trunk utilization - be able to see gateway and per trunk utilization for your SIP and H.323 protocols
Our team is also working on Avaya call managers & CDR support investigation. I would like to say big thanks to all who has helped us with this. It's important for you and we are listening, stay tuned for more.
Support for phone details polling - see all details of your hardware or software IP phone

We are also investigating Video IP SLA operation support - check your network quality readiness for video services.

In addition, we are also closely watching your Lync requests and how Lync growing in business sphere. It would be very valuable to leave your "Lync story" here or vote for this feature Microsoft Lync Support | thwack

thanks,

Michal

Find more posts tagged with

vnqm_roadmap

voip_what_we_are_working_on

ipsla_productblog

Accepted answers

All comments

Deltona

Please support both Avaya Red and Blue.

michal.hrncirik

Hi,

what's the difference between those two devices?

Deltona

Red is Avaya's own solution. Blue is the older Nortel (now Avaya) solution which was/is SIP based.

You can tap into both systems through the manager. There are tons of OID's that contain all the information you need.

Deltona

That was a quick reply as time was scarce. Here are some more details.

Avaya - Red: Has a traditional Call Manager

Avaya - Blue (Nortel): Uses CS-1000 as a traditional Call Manager, which uses http://en.wikipedia.org/wiki/UNIStim from IP Phone to CM.

CS-1000 is comprised of a bunch of blade chassis, server blades with Nortel's OS. Each server has different roles. Most of these CS-1000 blades have IP adresses and full support for SNMP. FWIW, CS-1000 can be configured to send traps as well, to the management station.

Here's a link to the Nortel MIBs:

http://support.avaya.com/downloads/download-details.action?contentId=C20101111114736410_9&productId=P0714&releaseId=7.5.x

Attached is the SNMP manual for the CS-1000 (r7.5)

Product link:

http://nectarcorp.com/cmp-modules/vendor-knowledge-modules/avaya-nortel-cs1000

michal.hrncirik

Awesome! thanks for tech. specs. we will definitively take a look on that and what it would mean for us to implement it.

thanks,

Michal

andrew.briggs

Great to hear about Video Services. Will this include Cisco TelePresence Endpoints, and CTMS. We have a lot of TelePresense units globally and it would be great to monitor the quality of the calls between them during our meetings.

thanks,

Andrew

michal.hrncirik

Hi Andrew,

we are currently investigating market and users needs so I can't give you more details about supported devices. But Cisco telepresence is on list along with polycom, and other HW & SW video vendors.

thanks for feedback,

Michal

sja

Juniper RPM support

I know it's I try to move IPSLA from the green group to blue.

/SJA

jspanitz

We've got a mixed environment so Juniper support would be fantastical

FormerMember

Would it be possible to add support for other VOIP gear like I3, Fonality, or the Asterisk PBX-in-a-flash? Our company has all 3 due to acquisitions and it's a real monitoring headache.

michal.hrncirik

Hi,I'll create an internal feature request for that. unfortunately these are not widely requested vendors for VoIP in VNQM. Feel free to create a feature request on thwack Ideation

thanks,

Michal

borgan

Are there any plans to add more SLA's supported on the Cisco Nexus 5-7K?

jerf

Are there any plans to add VOIP SLA's and support for Shoretel and Shoretel Director?

michal.hrncirik

Hi,

we will investigate why it doesn't support current IPSLA functionality (or better to say what's the difference between IOS versions).

michal.hrncirik

Hi,

it's on our roadmap but not with the top priority - that's what we have on our "what we are working on" page.

ctopaloglu

rams

FormerMember

You mentioned PRI utilization on SIP and H.323 devices - Is it safe to assume this will not monitor PRI utilization on an MGCP Gateway?

michal.hrncirik

we should be able to poll that. you may try Beta 2 that contains this PRI polling.

FormerMember

Thanks Michal - I don't currently have the resources to run a beta for this product. I will, however, upgrade when the actual release is available. Thank you for the information.

michal.hrncirik

Hi bhooper,

I just validated the functionality so let me clarify that. With VNQM as it is in beta - you will be ablt to poll PRI utilization on a cisco media gateway gateway (trunks, voip & data utilization). but you won't see details about SIP or H323 codecs.

It would be great to get your input on the data you may get from gateway via our beta 2 in your environment and how big role has information about codec for your use case.

thanks,

Michal

FormerMember

Juniper support would be a major enhancement.

carlgranger82

">michal.hrncirik Was support added for the Nortel/Avaya Call managers CS1000?
The specs and details were posted earlier in the post by Deltona

Thanks
Carl

michal.hrncirik

Hi Carl,

not in current Beta. however we are now investigating support for Avaya call manager S8700 and Avaya media gateway

foonly

Please use native Orion NCM credential database table, or at least make credentials editable.

Thanks!

FormerMember

Yeah that market is HUGE for those solutions :-) please spend time on that more than SIP/H3.23 KIDDING!

michal.hrncirik

this is actually very good request. currently we are trying to merge all the credential types across Orion platform to make it re-usable across products.

cbulleri

Is there an estimate time on when we can expect that the ability of integrating to Avaya CM will be available?

michal.hrncirik

we are working on it right now as a highest priority. unfortunately can't give you more precise date because of revenue recognition policy. but I would recommend subscribe in VNQM beta forum so you may watch the progress.

johnthomson

Hi,

We created the feature request bellow back in 2011, it may had too much scope and cover too many SW products to have been worked on.

We are unable to fully utilize the IPSLA tools due to the configuration of IPSLA's being an Admin task. Our SW environment consists of 7 pollers and we have engineers with different skill sets and training all over the world. We cannot give all engineers full Admin rights to configure IPSLA's as they may inadvertently change core functionality that can affect hundreds of clients.

Please, please have a look to see if you can change the level of user that can configure an IPSLA to a standard rather than Admin user, the rest we can patiently wait for.

Cheers

John

Feature Request Account Feature Limitation Builder

">johnthomson Jul 6, 2011 6:45 AM

Feature Request

Account Feature Limitation Builder

Please create an account feature limitation builder, the current choice of Admin, node management or read only makes it difficult to provide access to our engineers to customize the networks they are responsible for while maintaining the central admin rights of the system.

It would be great if we could go to an user/group account feature builder and create a new user level and then select options from a list of features and then go into the user/group accounts and pick from a drop down menu a predefined feature level.

I have put a quick list here as a starter for 10, depending on the feasibility /time lime to implement a full account feature limitation builder perhaps it would be possible to add some extra allow options within the account settings?

	Read	Clear Alarm	Add Device	Set Thresholds	Add IPSLA	enable CBqoS	Create MAPS	Create Accounts
Read Only	x
Level 1 Engineer	x	x
Level 2 Engineer	x	x	x	x			x
Level 3 Engineer	x	x	x	x	x	x	x
Admin	x	x	x	x	x	x	x	x

deverts

John,

While I like the request and feel it is justified, there might be another way to do this. You could push the IPSLA config to the router from NCM (assuming you have it), then manually import to VNQM. I agree, the Account Limitation Builder would be nicer, but the NCM/manual import will at least get your policies deployed and monitored.

mr.e

I support johnthompson's feature request 1,000 %... The current account and rights limitations are just not sufficiently granular I would very much like to see the rights defined just in the way that he described.

PS: John, you may want to submit this as an official Feature Request. If they let me, I'd vote for your idea 1,000 times.

johnthomson

Hi If you have been reading this request please take the time to vote for the implementation of the basic feature to allow non admins to create/ edit IPSLA's

Its has been two years since the topic was raised and there is no sign of it being developed.

Link to the Vote.

http://thwack.solarwinds.com/ideas/2752

michal.hrncirik

I can hear it clearly and loudly

planglois

The blue solution has SIP or UNIStim IP protocol

Network_Guru

I am troubleshooting a PCoIP issue at one site. I have 2 IPSLA responders at this site.

The problem appears to be "out of sequence" UDP packets arriving at the thin-client devices.

Looking at my shadow router in the HQ building I can see IPSLA stats on the router for out of sequence packets.

Can we get Orion VNQM to report this statistic as well?

Round Trip Time (RTT) for	Index 40008
	Latest RTT: 32 milliseconds

Latest operation start time: 22:27:01.373 GMT Wed Apr 2 2014

Latest operation return code: OK

RTT Values:

Number Of RTT: 100

RTT Min/Avg/Max: 31/32/33 milliseconds

Latency one-way time:

	Number of Latency one-way Samples: 100
	Source to Destination Latency one way Min/Avg/Max: 17/17/19 milliseconds
	Destination to Source Latency one way Min/Avg/Max: 13/14/15 milliseconds

Jitter Time:

	Number of Jitter Samples: 99
	Source to Destination Jitter Min/Avg/Max: 1/1/1 milliseconds
	Destination to Source Jitter Min/Avg/Max: 1/1/1 milliseconds

Packet Loss Values:

	Loss Source to Destination: 0	Loss Destination to Source: 0
	Out Of Sequence: 0	Tail Drop: 0	Packet Late Arrival: 0

Voice Score Values:

Calculated Planning Impairment Factor (ICPIF): 1

MOS score: 4.34

Number of successes: 2

Number of failures: 0

Operation time to live: Forever

Actually everything in the Packet Loss Values section would be helpful to display in Orion.

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipsla/configuration/12-4t/sla-12-4t-book/Configuring_Cisco_IP_SLAs_ICMP_Jitter_Operations.html#GUID-697D0831-30FD-4136-9009-966A3D6E865E

Each ICMP packet includes a sequence number in its header that is used to count the number of packets received out of sequence on the sender. Both the sequence number and the receive timestamps can be used to calculate out-of-sequence packets on the source-to-destination path. If the receive time stamp for a packet is greater than that of the next packet, the first packet was delivered out of order on the source-to-destination path. For the destination-to-source path, the same method can be applied. Note that if the packet is out of order on the source-to-destination path, it should be returned out of order to the sender unless there is also misordering on the destination-to-source path