I think the best would be you to get in touch with your contact person at Sevana that is providing support for your AQuA license. In this example we were using pre-built PJSUA and config files were stored in the same folder as the PJSUA executable.

Thanks,
Admin

we currently have a license to use Sevana voice quality tool and I am thus greatly interested in using PJSIP to automate tests and send wav files. I have sucessfully built PJSUA and after running it, I can use any commands that are shown on the screen such m (make call), h (hang call) etc etc. I have even sucessfully registered to my SIP provider using the +a (create account).

Unfortunately however I cannot use any of your commands (–help, –aut-answer 200 etc.) or run the config file through your command. Am I doing something wrong? What is the actual command that you have to issue on the command line interface? Where do you place the .cfg file? Are you using PJSUA application?

Thanks in advance,
Kris

Please note this campaign ends on December 31, 2011. Starting from January 1, 2012 all prices will be in Euros for all customers globally.

Thank you for your interest in Sevana products and services!

We have not published the roadmap due to certain reasons, but the plan is that most of functionality demanded by the market will be implemented by the end of 2011. Here is a quote from internal roadmap for this solution:

- Alerts (notify to email on MOS going down under threshold) – available
- Conference room testing – available
- Help section for online product help – available
- Blast dialing to evaluate voice quality depending on the calls load sent to the server under test – available
- Implement “reasons display” for failed test calls. Show q.931 cause code for unsucessfull – available
calling and table with description in help section
- Show audio wave-form for original and degraded audio

0.3 – 30 March

- Reports (pdf, email and print) – not ready yet
- Use Cisco IOS capabilities as echo-server emulation – cannot be implemented due to non-documented device features
- Sniffing traffic, sent from VQM (only outgoing self-made tests) – available
- Analyze call using Wireshark (opening the .pcap file your system must save for each call) – available
- Multiples users support (ability to have user specific tests) – coming soon
- Alerts (SNMP traps) – available
- Make system stable against SQL injections – available
- Automatically clean recordings/captires to not waste space on HDD (global option for
storage time) – available
- Initiate Dials via Web Service. All calls should be initiated by HTTP POST (even internally) – coming soon
0.4 – 30 July
- Full sniffer support (dedicated sniffing interface) – partly available
- Add option to set CallerID on outbound test calls
- Possibility for adding multiple schedules for test execution (ex. Mon, Fri, Sat, 8am-9pm, every
10 minutes)
- Add option to set Codec for calling (SIP option) – available
- More alert types (PDD, packet loss)

Also, what’s the timeline/roadmap for the product release?