pythonpoole

I don't think there is a way to change this. If my memory serves correctly, someone asked about this a while ago and the response was something to the effect of: 6 rings is a fairly long time especially for a softphone, is more time/rings actually needed?

6 rings is pretty standard for a lot of lines, and the assumption is with a softphone that you'll be close to the computer when it rings. If you really do need more ring-time however (I'm not 100% sure), but perhaps if you used Axon and configured it so Express Talk was simply using an Axon extension for the default line, specifying the time till voicemail forwarding for that extension in the Axon configuration interface might prevent/change the time/number of rings before Express Talk sends the call over to voicemail etc.

I think you mean Express Talk.

Anyway, the configuration is fairly simple.

1) Create an extension in Axon and choose a username and password, the display name is just for your own personal reference

2) Open express talk, under the line settings put in the username and password you chose in step 1 and use the IP address of the computer with Axon installed as the Server

3) Optionally give yourself a friendly display name that will be used for caller ID purposes, and simple click ok to apply the settings

The following variables are built-in

%time%,%date%,%cid%,%callername%,%linenumber%,%did%,%drn% and %linename%

You can also define your own based on OGM events

Thank you for the heads-up on the automatically adjusting registration frequency, I didn't realize it did this, and I guess I just made the assumption (because I had a similar problem a long time ago with some VoIP hardware I had and changing the timer fixed the problem).

Here is a copy of a section of the email I sent you, TJ

My third problem I have posted on the forum and its to do with a VoIP service I'm using that works fine when Axon has just been opened, but after a while (couple of minutes I'm estimating), incoming calls stop coming through to Axon and go to a voicemail/unavailable message from the provider. At first I thought it had to do with timings, because I have had problems like this with other VoIP equipment and changing the timing to 60 seconds fixed the problem, but as I see Axon automatically adjusts the timings, that isn't the problem. I looked at your TJ's suggestions (above), but I have portforwarded all the mentioned ports to the Axon computer and run the setup wizard and still no luck. In fact I went as far as turning off the firewall on the router (temporarily) and keeping all ports forwarded to the Axon computer, still no change. All other VoIP accounts were working as normal, but this one still had (and has) the problem after a few minutes.

Oh ok, I didn't realize. I didn't really read over it to see if it had been updated, it just seemed to look different to the last time I saw it so I just made an assumption. Unfortunately I have a SPA3000 adapter so I can't be of much asistance if the problem is unique to the 3102 device, although I'm sure someone has gotten it to work right around here.

I have written the sem-official guide to setting up the SPA 3102 with Axon. (It is a pinned topic in this forum). NCH then took my guide and used it as the basis of their new guide for setting up the adapter (found on the NCH website under hardware support). Either method should work, and they differ only in a couple of areas.

So I suggest you refer to one of those guides first and then see if you can get it working.

For the dial plan you'll be able to set it up so when the number starts with 0, it can be forwarded to the physical exchange (your PSTN line), otherwise use another line or dial the number as an extension.

You'll also be able to configure it so any calls that come into the SPA 3102 FXO adapter will be sent through Axon and will ring the a chosen phones throughought the campus.

If you need more information just let me know.

I don't have much experience with transferring from an analogue modem line to a VoIP line.. with all voip lines its very simple, you just enter the number (or extension) on Axon you wish to transfer the call to and it works flawlessly (at least for me). Although I do remember once when trying something similar with a PSTN line that it didn't work out, for some reason the transfer couldn't be completed.. I'm not exactly sure about that though, I can't remember any more.

From what I know, STUN servers are used with by all VoIP software / hardware, not just NCH's IVM/Axon/Express talk software.

Stun servers simply used to discover what your global IP address is so your voip equipment can be used to communicate with external voip services.

You can't just "retrieve" your global IP from Windows, you can only retrieve the private IP. To obtain the public IP of your network you need to connect to an external server (e.g. when you visit http://whatismyip.org) which then feeds back your public IP address so it can be used by the software on your computer.

No personal information such as your name, email or OS settings are sent to the Stun server, it's a pretty anonymous process.

If you prefer not to use STUN, there is the option of using UPNP to disocver the global IP address, but this only works in certain instances with hardware/modems that support upnp devices.

The other option is to specify the address manually (i.e. you go to http://whatismyip.org) find your IP address and enter it in the textboxes. This is not a recommended method as most likely your IP is dynamic and changes every so often and that would meaning having to manually change it each time your IP address changed (possibly multiple times a day).

For stability I recommend you use 2003 or XP. Many businesses also seem to use 2000 which seems fairly stable, although a bit outdated to be starting with now. Personally I have had IVM work fine for me on XP with no troubles.

Hi, I recently signed up for new VoIP service. Axon registers with it fine and calls in and out are no problem. Unfortunately, after a while (only about a couple minutes I'm estimating) incoming calls stop getting routed through to Axon. If I close and re-open Axon it works perfectly fine again for a little while and then simply stops responding to incoming calls and the caller is taken to an unavailable/voicemail message.

At first I thought it was a registration timing problem, but that however is incorrect as TJ has said below, Axon adjusts its registration frequency to what the service requests. (For some reason this version of IPB doesn't let you change your topic title for some reason (old versions of the board do let you)).

I have gone through the Axon Network wizard and went as far as to portforward all ports to the Axon computer and even tried with the router's firewall off for a little while. Still no luck, Axon shows know recognition of incoming calls after a few minutes.

Thanks for your time and help,

~pythonpoole

Unfortunately, I don't think it is possible for the end user to configure/modify the webpage styles or content. If you contact NCH however, they may be interested in creating a custom version for you with your own graphics / content (at a cost). If I remember correctly NCH does offer this service for some of their other software like IVM.

I do not know exactly what the problem could be (I haven't tried Engin yet), however there are some things to take note of. Namely, Axon does not support the G729 codec. This means the Engin service must be able to also support standard alternative codecs. Most VoIP providers do support other codecs, and simply pick one as the 'prefered' codec if available on both ends, but negotiate with other codecs when necessary. Therefore, I do not think this is your problem unless Engin does in fact only support that codec.

Can you provide the error that Axon is giving when attempting to register with the service?

Yes you can. Just download the latest version IVM. It comes as a fully functional trial and you can test the web interface yourself.

Then create 10 extensions and 10 external lines set up with each of your voip cheap accounts.

Create a new group (eg 702) adding all 10 extensions to it.

On each external line set the "Incoming calls ring on extension or group" option to the group you setup above (eg 702).

Now if a call comes in on any of the 10 lines, all extensions will ring, and whoever answers is it first gets the call. If someone is already on the phone, if their softphone supports more than 1 line they may get a pop-up message indicating someone is calling on line 2.

Now in the Advanced settings for the first external line, go the the "Chain to Next Line" section and under "If call fails on this line, try line", select the second external line. Now do the same thing but for the second external line, but this time, set it to use the third external line if the call fails. Then do the same for the 4th and 5th and so on. You can either leave the 10th alone, or set it to try line one again, so it keeps going around in a circle trying to find an unused/operational line to call on.

Now, when someone calls out.. it first tries line one, but if busy it tries line two, and if thats busy it tries line 3 and so on until it reaches line 10 and then goes back and tries again and checks if line 1 is busy etc.

Now you just need to setup the default dialing plan so either the default external line is set to the first voipcheap line, OR you have created dialing plan rules so for example if you start dialling a number with 9 it routes the call to the voipcheap lines.

If you need any further explanation, don't hesitate to ask.

Well you cannot have multiple locations/softphones registered to the same VoIP or Axon account. The whole point of Axon is to allow you to take one VoIP account and split it amongst many extension accounts.

I think what you are trying to accomplish is:

Each client has a single Axon extension which they can use to phone in and out of the available VoIPcheap lines.

Basically you probably want to set it up so if line one fails or is busy, use line two

if line two fails or is busy, use line 3, etc.

This can be done in Axon when configuring the settings for external lines (can't remember, may be in advanced options). There should be an option to automatically use a secondary line if the line becomes unavailable for whatever reason.

P.S. Unless you're operating a call center, it is very very unlikely that you would be using 10 phonelines at once. In your average small-medium sized business 2 external phonelines or channels should be fine for 10 people.

IVM isn't exactly intended for receiving faxes etc. However I do agree that fax support would make a nice addition to the software.

Right now IVM has a "Fax tapi handoff" mode, which simply means IVM won't answer a call if it is a fax and will allow for other Faxing software to intercept the call and receive the fax. I've never tested this, and that is only an assumption.

IVM is free for a trial period only, after that you must purchase a license, and because you want the outbound dialing feature, you will need at least the Small Interactive System license (see here for different licenses http://nch.com.au/action/reginfo.html#ivm).

You will be able to have other programs make IVM call out and deliver a message, for example:

Execute: IVM.exe -outbound 5551234567 -set “testing=haha this is my message"

And then have outbound calls play an Out Going Message that is set to read out what is stored in the variable testing.

So all you need is away to get your webserver to execute the IVM program with the appropriate arguments and it should work fine.

No, its a Faktortel line.

It is on, it does that all the time but answers fine. For some reason lets say I have it set to pick up after 5 rings, for the first 5 rings it says not answered, answering mode off and then answers on the 6th ring. That's fine and it works perfectly with my other lines (VoIP and Voice Modem). The problem is this:

20:27:12 Call has disconnected

20:27:12 Call disconnected

20:27:12 Call has disconnected

20:27:12 Call disconnected

20:27:12 Call has disconnected

20:27:12 Call has disconnected

20:27:12 Call disconnected

20:27:12 Call has disconnected

20:27:12 Call disconnected

20:27:12 Call disconnected

That is all the same call. When I get any other line to go through the same OGM, same conditions and everything it answers fine, however this particular VoIP line just refuses to answer and just continues to put "Call has disconnected" and "Call disconnected" in the log as the line is still ringing.

When a call comes into axon on one of my lines it will not play the start prompt or the ringing chimes, fine, so I set it to basic ringing.

However, look at what happens to IVM when the call comes in, it refuses to answer and comes up with a log like this:

20:27:02 Incoming SIP call

20:27:03 Incoming SIP call

20:27:03 Incoming SIP call

20:27:04 Incoming SIP call

20:27:04 VoIP Voice Mail ********** [Not Answered, IVM answering mode is off]

20:27:05 VoIP Voice Mail ********** [Not Answered, IVM answering mode is off]

20:27:05 VoIP Voice Mail ********** [Not Answered, IVM answering mode is off]

20:27:06 VoIP Voice Mail ********** [Not Answered, IVM answering mode is off]

20:27:09 Incoming SIP call

20:27:11 VoIP Voice Mail ********** [Not Answered, IVM answering mode is off]

20:27:12 Call has disconnected

20:27:12 Call disconnected

20:27:12 Call has disconnected

20:27:12 Call disconnected

20:27:12 Call has disconnected

20:27:12 Call has disconnected

20:27:12 Call disconnected

20:27:12 Call has disconnected

20:27:12 Call disconnected

20:27:12 Call disconnected

Is there any way of fixing this?

Yes, nchtj, that's fine. Please feel free to use any part of the guide I have written.

Thats not a very good response to the problem nchto.

Since Vista is new, most users will look at that, see that it works on pretty much all Operating Systems, and make the assumption that the page just hasn't been updated yet to include Windows Vista. Users will not be happy when they download and find out they get the Blue Screen Of Death and cannot even use their computer anymore until they restore/recover.

I agree with the article poster, there should definitely be a warning on the uplink page.

It should still keep all your line settings when you close and re-open. Make sure default line settings isn't ticked on any of the different line configurations. If in fact this is a bug, you may want to contact NCH directly.

The problem with voip lines is each extension has an individual connection to the call manager vs an analogue line where all devices sit on the same line, so if one device answers on that line you can use another device on that line to monitor that active line.

Answering the call after it has already been forwarded is not possible with voip because each of the phones has their own virtual line sort of thing, and when a call is not answered the call is forwarded to a different line (not just answered like a modem), and from there IVM answers the call. The only way to have multiple voip phones on the same line would be to have a conference call, and I really don't know of anyway of getting IVM to conference call with another extension while its actually taking a message from someone.

Yes this software does work with VoIP lines.

However here is the deal, the Vonage company doesn't like users using other hardware or software with their phone lines.. they're kind of mean and make you purchase their hardware for their line, even if you have other hardware (or sometimes even the same hardware) that would work perfectly.

Most VoIP providers are not like Vonage and they are open to BYOD (Bring Your Own Device) which allows IVM and other software from NCH like Axon to easily connect with them.

Does that mean there is no hope for using Vonage with IVM!? No! There is hope!

Method 1: Purchase a Voice Modem, connect vonage line to Voice modem

Advantages: Very cheap, ~$20. You may even already have one

Disadvantages: Quality not as good as other methods, but still acceptable

Method 2: Purchase a Voice Logic Board, not sure what they're called

Advantages: High quality, usually support many phone lines, with Carousel software may be able to interface with Axon

Disadvantages: Very expensive (compared to a normal Voice Modem)

Method 3: Purchase a Sipura 3000 or 3102 FXO adapter

Advantages: High quality, makes any normal or Vonage line into a VoIP line the computer can interface with, also can be used with Axon to have an even more advanced feature-full phone system

Disadvantages: More expensive than a voice modem, a little complicated to set up

Method 4: Buy a Vonage SIP line (Vonage lets customers purchase SIP lines that IVM and Axon can interface with)

Advantages: Would be perfect solution... but

Disadvantages: Vonage only offers an SIP line in addition to your current plan, you can't have just an SIP line. Also your SIP line is completely seperate to your Vonage line with a seperate phone number and seperate calling plan. No unlimited calling plan is available for Vonage SIP lines. So in summary, you would have to pay for two vonage lines, even if you only used one.