pythonpoole

It's more likely appearing because your device is asking axon to subscribe but axon isn't setup for voicemail. The solution would be to disable the MWI feature on the device so it stops sending subscribe messages.

hmm ok, I'm so used to IP phones and ATAs having web interfaces I just made the assumption this did too. I really have no idea though, sorry. You can try adding line1_authname: "121" to the config, but I doubt it will make much difference. One thing to watch out for, I noticed you're using port 50970. Apart from the fact that it's really high, Axon is also known for some problems on non-standard ports. Perhaps try using 5060 or 5061 to see if it makes any difference. Also in the first SIP trace you gave.. is it just me or was there no password transmitted in the trace?

This is an issue that has been brought up a few times. My understanding is that when Axon puts receives the command to put a call on hold, instead of just handling it internally (e.g. passing it on to IMS and leaving it at that), I believe it also signals the provider (in this case PennyTel) anyway to start the 'hold' regardless of what hold options are set-up in Axon/the extension. For some providers, they simply ignore this on-hold signalling.. other providers sometimes decide to take over and automatically start playing their own (sometimes unlicensed) music. And lastly (as it appears in this case) many providers decide to take over and put the call on hold on their end but don't provide any music - leaving the caller in silence. I've mentioned this problem before to NCH so hopefully an option to turn off the signalling will be present in future versions.

What you can do is set variables in IVM and have IVM read out those variables when it calls you. To set a variable, execute with the parameters -set "myvar=haha" As for the PHP function, I think it is exec(). You may need to modify your PHP settings/permissions though to allow it, I'm not sure.

I think the major problem is this line: To me this is saying that your IP phone is not using the username/extension number set-up with Axon, but is instead sending out the username 'UNPROVISIONED' this would explain perfectly why Axon is reporting that no such extension exists. Make sure both 'Username' and 'Authorization Username' (or something to that effect) are both set to your Axon extension number. I suggest you go into advanced mode of the web interface for the phone (if there is one) and scrutinize for any instance where the word UNPROVISIONED appears. If you cannot find such an instance of the word, perhaps contact Cisco and ask if it means anything. Also, perhaps I or someone else can help better if you provide the configuration file for the phone. (i.e. in firefox browse to the web inteface and save as..).. if it is anything like other Cisco/Linksys products it usually saves the whole configuration as an HTML page which someone else can then open up and refer to.

Hmm, it's not the first time someone has complained that administrative access is requried when they are already an admin (this seems to only happen for Vista users). We'll have to see if this gets fixed in the future. Anyway, you can disable Express Talk (and any other programs) from auto-starting by WINDOW KEY + msconfig + ENTER (i.e. type msconfig on the start menu). Now go to the startup tab and uncheck anything you don't need. You can also go to the services tab, click 'Hide Microsoft Services' and again untick anything you don't need. Hope this helps.

Yeah there is actually. IVM lets you control the software functions using the command line. You can read about the full SDK here, but the basic idea is: executing ivm.exe -outbound 5551234 will make IVM dial out to 5551234 and play a pre-defined message (that could even contain variables like the person's name/num etc). If you're using PHP for your website's code, it has a function to execute external programs with parameters (assuming your webserver and IVM are on the same PC) and you can use that to control IVM. If both are not on the same pc, you can install PHP on your IVM computer and then have your website send a request for a php page on the IVM PC which is programmed to execute IVM and call you. Not sure if you understood all that, I don't really know what your level of programming knowledge/experience is, so let me know if you don't understand.

I'm not sure, but usually the word subscribe refers to message waiting indicators. It is possible that the phones are trying to subscribe to MWI but you do not have any voice mail system like IVM set-up to handle this.

Well I don't have much time (have a test to study for and it's late), but here is the basic instruction: In Axon's web interface, first create or edit an extension in Axon for your PAP2. Axon comes with a bunch of default extensions you can get rid of if you want. You can also choose to use one of the default ones or create a new one. Either way just so long as you note down and set a password for one of the extensions you should be good to go. Next go to External Lines and create a new external line for each SIP account you have (you may want to delete the default lines that come with Axon if you don't plan on using them). For each external line you'll be able to enter the required username, password and server address for each VoIP provider. Set each external line to ring to the extension you just set-up. The next step is to login to your PAP2's web interface. The basic minimal settings to change are the username, password and proxy/server. The username should be the extension you setup in Axon (e.g. 101), the password should be the password for the extension, and the proxy/server/domain should be the IP address of the PC running Axon. *P.S. If you don't know your PAP2's IP address to access it's web interface, I believe you can get it by dialing **** rapidly on the phone connected to it (even if there is no dialtone) and it should present you with a menu. If I remember correctly, option 110# is for retrieving the IP address. If all else fails, you can use your router's DHCP table (if it has one) to try and figure out the IP that way. After you submit, the PAP 2 should register with Axon, and your PAP2's status page should show this. You should also get a dial tone now. The last step is to configure your dial plan. Go back to Axon and edit the default dial-plan. Set the default line to use (at bottom) to your default line (i.e. betamax). Then create a rule such that when you dial x as a prefix, it removes the x digit(s) and sends the call out on the vbuzzer line. *Note: You probably do not want to use # to separate your dialling as for many ATAs (including the PAP2 I think) dialling # immediately aborts dialling. Instead use an uncommon prefix or an unused area code to differentiate them. E.g. in North America you can set the prefix to 00 since there are no numbers that start with those digits, in Australia I think 1 would do.

Error 401 (Unauthorized) means the phone is connecting to the Axon server, but the extension number or password is wrong. Make sure you create (or edit) an extension in the Axon web interface for the phone (e.g. 121) and then set a password you will remember. Copy over the username/extension and password exactly into the phone's web configuration interface and you should be good to go. The error "Unknown ID trying to register" usually is indicative of a phone that is trying to register with an invalid/non-existing extension. In general Cisco and Linksys products work pretty well with Axon and you shouldn't have too much trouble after you sort out the authentication error.

I'm not really sure. 95% of the time 1 way or no-way audio problems are related to conflicts with the network configuration (e.g. ports not properly forwarded) I also know that from my time here the 'hold' function seems to be very flaky in the sense that I have had reports where it causes audio to drop 1 or both ways and other reports that say putting the call on hold and taking it off hold actually restored audio both ways for people who had audio trouble before the call was put on hold So basically I'm sorry to tell you I have no idea and it's a big mystery to me. However I believe Axon has a setting now (advanced line settings I think?) that is supposed to correct some instances of one-way/no-way audio problems. See if that helps?

Well firstly make sure you don't have 2 PCs running the software at the same time with the same VoIP/SIP account. This can lead to problems/confusion with authentication and cause unexpected behaviour such as rejected calls. However the problem could also be related to your network configuration. If Express Talk is not able to properly signal to the VoIP server that it wants to make an outbound call, Express Talk may be stuck trying to negotiate with the server leading to what seems to be a call to nowhere. Be sure to open the appropriate ports on your PC and router's firewall(s) and then run the 'Network Setup Wizard' in Express Talk. The last possible cause (and I know people don't like to hear this) is human error, whereby a simple mistake such as the way the number was dialled leads to a pre-mature assumption that the problem is related to the software (although this probably isn't the case here).

RFC2833 is one of the ways I was talking about for transferring DTMF responses. I guess if IVM isn't receiving the responses, perhaps it doesn't support this method. Can your provider set it to a different option to try and find one that is compatible (the only other one I remember is SIP Info.. and I don't know which one(s) IVM supports).

You might have to look for a TAPI compliant telephony board that supports T-1 lines, I don't know of any off hand, sorry.

Are you sure you have permissions to write files to the LAN folder, or just read files? Sounds like the folder has permission/right restrictions.

This is probably because unlike analog systems where it is a simple 'tone' system for key responses, VoIP actually has about 3 or 4 different ways to send key responses to the other end (in this case IVM). If it is using an incompatible method, IVM will simply ignore the key presses. See if your VoIP provider can adjust the DTMF options and try different settings to see if it will work.

You will still have access to the other mailboxes. This can be done either through a) Calling an internal extension set-up for retrieving voice mails Calling in from outside and at your IVR menu, select an option (e.g. *) to access voice mail c) Using the built-in web interface in IVM to access voice mail with a web browser - As for faxes, you shouldn't have any problem sending them out. Simply connect the fax to another phone jack on the same line, or to the same phone jack as the PC by using a splitter (The Fax machine needs to be connected directly to the phone line from your Telecom, and not to the Telephony Board or Axon).

*Before I forget, there is also other way to connect your analog phone line to Axon. There are devices called FXO adaptors (e.g. the linksys 3102) that basically link analog phone lines to digital phone systems like Axon. Carousel is refered to as a virtual FXO adaptor because it takes the analog audio from the telephony board and links it to Axon in a digital form, but other people chose to simply purchase an FXO adaptor that completely eliminates the need for a Telephony Board. FXO adaptors are generally cheaper than telephony boards, and also provide very similar functionality and do not require the conversion software to constantly run on the PC. Unlike a telephony board however, they are not installed in the PC, but rather connect to your network through ethernet much like an ATA adaptor does. So it's up to you what you would rather do. - Recommended specs really depend, and I don't have a definitive answer for you, sorry. I know that I run a phone server that has a 2.5 GHZ pentium 4 (single core) processor and 1 GB ram and it handles several simultaneous calls with a fair amount of resources to spare. I would recommend these minimums: On 2000/2003/XP: 2 GHz single core or better processor, with at least 512 MB of ram On Vista: 1.7 GHz dual core or better processor, with at least 1 GB of ram - As for your list, that pretty much sums it up quite well. - Axon is very straightforward when it comes to installing and setting it up. It has a Web based interface and adding extensions, modifying dial plans and configuring dial groups are just a couple of clicks away. Compared to many other PBX call routing systems, Axon is very much 'dumbed down' and user-friendly so you've probably made the right choice. IVM connects quite well with Axon, in fact when you install Axon I believe it automatically sets-up IVM with an extension and voice-mail accounts. If not, it could be the other way around where if you install IVM second it auto sets up. Either way it's not that difficult, and even if you need to set it up manually, it's practically a piece of cake. Carousel is a bit tricky to set-up in comparison to other software however. Even I (as an 'Einstein' according to the forum) would have to spend some time looking through the manual/documentation. It's not so much that it's very complex or has too many settings to configure, it's more a case of understanding what the settings need to be configured to. Either way though I would say FXOs (virtual or otherwise) are a little difficult to set-up for the average user and you may need to seek advice/help later on for this part. - Note that some IP phones have built-in router & bridging modes so you can actually connect the phone to the switch, and then a PC to the phone so you don't need to run another line and take up extra ethernet ports. - Lastly, the mailboxes run independently to the number of lines, extensions or IP phones you have. You can have as many or little as you need (*limited by your IVM license), but realize that only 1 mailbox can be connected to each IP phone (i.e. so when that IP phone's extension is called and not answered, it goes to its connected mailbox).

You're correct, both the PC and the individual IP phones would connect directly to the router via ethernet. When a call is made on an IP phone, it is then sent through the router to the PC with the telephony board, and vice versa, when a call comes in it gets sent from the telephony board to Axon running on the PC and then through the router to the appropriate IP phones. It's not quite 'automatic' though. Each IP phone will have its own extension. In Axon you will create those extensions and assign them a username and password. Each IP phone can be configured with a username and password to 'log-in'/authenticate itself to the PBX (Axon in this case) to make calls. The rest of the network would remain unaffected. However if you don't have enough ethernet ports available on your router, you would need to purchase a network switch to add more ports. Another note for the network side of things, if your router supports QoS (quality of service) it may be a good idea to turn this feature on as it may help prioritize IP phone traffic to ensure the sound doesn't start breaking up for example if the network becomes busy with other data traffic.

Basically there are two methods to go about doing this. 1) Using digital IP Phones IP Phones are a new generation in technology. Instead of transferring your voice in an analog wave form to your Telecom, digital IP phones convert your voice to a digital transmission and send it over your network or Internet connection to the receiving computer. They also tend to support additional features like call transfer, hold, conference and sometimes intercom buttons. Typically most IP phones also support more than 1 'virtual line' which lets them take or make more than 1 call at a time and easily switch between the lines as necessary (obviously you would not be able to make or take any more external calls at a time than you actually have phone lines for) **Technically IP phones can also be called VoIP phones since they transfer voice transmissions over your network. In this case however, all transmissions would be 'in-house', so the type or speed of your Internet connection would have no effect on the performance of the system. IP Phones can range in cost between $50 and $500 (the high-end phones tend to have things like colour-touch screens, built-in 'smartphone' type software and webcams) A full-featured, solid quality IP phone usually costs about $100 or more, although the GXP-2000 is a great phone with lots of functionality and can be obtained for about $85 IP Phones connect directly to a free Ethernet port on your network router or switch. 2) Using Analog (your existing) Phones/Handsets For this method, you need what they call an ATA adaptor. ATA adaptors basically allow you to connect traditional analog phones (the type you already have) to a digital IP phone network (like the type Axon supports). ATA adaptors generally cost between $35-$75 The higher-cost ATAs usually support more than 1 phone extension, so you could have 2 independent phone extensions plugged into the same adaptor. ATA adaptors also connect directly to a free Ethernet port on your network router or switch and then allow you to attach and run a normal (RJ11) phone line from the adaptor to wherever you want that phone extension. You can also use a splitter to have more than 1 phone share the same extension.

Even if you could reset the counter, I wouldn't recommend it. IVM likely uses it to distinguish calls (like an ID), and reusing the same identifier could have unwanted effects depending on how IVM is programmed. I still think the best option is to use the built-in OGM feature to build daily logs (e.g. Use log_%date% as the filename and then put in a character (e.g. 'a') to be logged for each call). The result is a log file for each day that has a character to represent each call. If you open the file in a program that has a character counter, you can easily check the number of calls for the day.

It's quite simple really, there is a dropdown menu right on the main IVM window that let's you change the answer OGM. In addition, each line can have a different answer OGM by setting one in the line settings dialog.

I wrote up a huge answer & explanation on my iPhone, but it didn't submit Oh well here I go again. - Ah, I see. So you would like to set-up an internal phone network with different phone extensions? To do that, you will need both NCH Carousel (free) and Axon. The purpose of Axon is to handle, manage and route calls on an internal phone network such as those found in businesses or hotels. Carousel is used to bridge analog calls from your Telephony board to the digital call type Axon works with. You can then create internal extensions in Axon as needed that can access the phone network, call other extensions or make/take external calls. Each Axon extension can either be in the form of an IP phone (which connects directly via ethernet to your network router or switch), a USB phone which integrates with softphone software on an existing computer on your network, or an ATA adaptor which allows you to connect normal analog phones to Axon. Axon was also built to work with IVM, so it is easy to configure it for voice mail etc.

The boards connect just like old dialup modems. A phone line runs between the phone jack and the phone port on the board (which is installed inside the computer running IVM). It's pretty much the same as connecting a normal telephone, except that the board is in place of the phone.

These are some of the boards NCH recommends: http://www.nch.com.au/hardware/telephony.html If I were you, I would look around and maybe ask some users on this forum what kind of experiences they've had with different Telephony boards. I can't personally recommend a particular model since I don't use telephony boards, or rather I don't use them with IVM, so I have no experience in the matter. I know that some users report mixed results with some boards, while others seem to work flawlessly. Basically the board acts just like a modem, you install it in one of the available PCI slots on the PC with IVM on it (or hook it up via USB if it is a USB version). IVM should then detect the Telephony Board when you go to add a Telephony device in the settings window. You will likely have to install the driver that comes with the board/modem first for Windows to detect it although some boards/modems may be detected automatically under generic chipsets. Even if your board is automatically detected by Windows, you should always install the latest driver from the manufacturer to help ensure full compatibility.