Jump to content

pythonpoole

Members
  • Posts

    842
  • Joined

  • Last visited

Everything posted by pythonpoole

  1. Is there any way you can post your SIPURA configuration settings? You can do this by going to your sipura page and going to File > Save as or Save page as... Then simply upload it somewhere for us to see. If you can provide that I may be able to identify the problem. Also if you can give a brief overview about what you have done with axon that would be great to. Also if possible, please note down what the Axon log says when 1) You attempt to make a call out through the adapter. 2) When there is an incoming phone call to the FXO adapter. I should be able to get it working for you if you can provide some of these details. I realize the guide is long and its very easy to skip or misinterpret a step which could prevent the whole thing from working. About the username/passwords, just so long as these are exactly the same as the username and passwords you setup with the extensions, you shouldn't have a problem.
  2. That is strange, I haven't had the problem. I recommend downloading and installing a new email client that is (I think its called) MAPI compliant, allowing software to interface with it and send emails. One example is Eudora. Once you do that set it up with your email account and set it as the default email client. Restart, and when IVM attempts to send emails it should go through Eudora instead so there will be no Outlook error messages. You can also specify the mail server in IVM so its hooked up directly to your email provider, if you do that it skips the client program like Outlook and Eudora and sends the message itself. Ok, first of all that won't really work, you can't just merge the two lines together with a splitter piece at the modem or whatever you seem to be doing. And if you have the modem phone cable on the second pair of wires and the other one on the first pair unless you have a 2 line voice modem it won't detect the one on the second pair. To get to my point... using the modem to answer the VoIP call is useless. It is actually more inefficient, lesser quality and redundant. IVM was built to answer VoIP calls. You can setup IVM with your VoIP account and give it direct access to the line over the network rather than the voice modem, when a call comes in IVM answers it without problems. I also recommend the use of Axon (a free software from NCH) which allows you to setup a call management system (PBX) on your network. For instance, if normally your VoIP calls go to your router, and then to a phone connected to your router and/or the voice modem, instead of this, setup Axon to use your voip account. You can then hook up a phone to your VoIP hardware and have it register with Axon. Then axon can be instructed to perform almost any action you need, the possibilities are nearly endless, you can make the call go straight to IVM (IVM will also register itself with Axon, and then if you set it up Axon can forward all incoming calls directly to IVM). You can also have Axon ring any of the phones connected/registered to axon, whether it be a softphone, or a phone connected to an ATA like your router. IVM can even forward a call on to phones or extensions setup with Axon so if a user phones in and they want to talk to a person you can immediately transfer the call to the phones set up with Axon.
  3. Hi, I think this should have been posted in the Axon forum actually. The way it works is, the SIPURA adapter never actually deals with IVM, everything is done through Axon. The SIPURA connects to Axon, Axon connects to IVM. Anyway, please check out my "Ultimate guide" to getting your SIPURA adapter to work with Axon (and other NCH phone applications like IVM) here: http://nch.invisionzone.com/index.php?showtopic=5091
  4. I don't know for sure, but it sounds to me as this is a case of the VoIP provider not liking ATAs or softphones that don't register every minute. I've seen a similar problem before, and it was a simple case of forcing the software to re-register every 55 to 60 seconds. However as far as I know, I don't think Express Talk has that option. :/
  5. Your VoIP provider has control over how many communication channels or number of simultaneous calls can be made at a single point in time. Most provider offer only one or two channels, some offer more but at a cost. Basically Axon is not limited to how many incoming or outgoing simultaneous calls it can make or take as far as I know, so if there is any limitation it must be on the service provider side.
  6. Try installing the older version you had by running it compatibility mode for Windows XP (right click exe > properties). The program should run and install normally. With any luck it should work. This is obviously only a temporary solution until the NCH staff can address this problem.
  7. You will need one FXO adapter per ordinary PSTN phone line you wish to connect to your new phone system. If one is dedicated for fax calls, you probably shouldn't waste money on an FXO adapter for that line, you can easily just leave it how it is with a normal analog phone attached to it to use if absolutely necessary. Basically how it works is you install Axon (free pbx software from NCH) which connects to all the FXO adapters on the network and converts them to "external [phone] lines" for you to use. Your USB, IP, and softphones connect to the PBX software and you can have any number of configurations. For instance, you can have all the FXO adapters added to Axon and make it direct calls from any line through to all the USB phones. If someone is already on the phone you can have it automatically ring the other USB phones that aren't in use in the office, or put them on hold until someone is available to answer. You can also have the option of choosing which line to dial out on through the USB/IP/Softphones. For instance you can make it so if you start dialling by pressing 1 first, then use line 1, two first then use line 2. You can also call the other phones inside the office internally if needed. The configuration possibilities are nearly infinite. In terms of cabling, the USB phone doesn't need to be connected to the central computer, but it does need to be connected to a computer, any computer on the same network as the computer with Axon and IVM will be on. If you get an IP phone rather than a USB phone, no computer is needed, but you do need Ethernet cabling from the phone to the central computer with Axon. Ethernet cabling can go up to about 300ft or more without any connection problems, signal strength loss or anything that may cause voice quality loss. USB cables can go a fair way to without problems. The only cable where length can affect quality is the standard phone line cable. So the distance between your phone jack and internet modem, or the FXO adapters should be about 6ft or less if possible, however 10ft or even 15ft shouldn't cause any issues.
  8. I think what you would like to accomplish will require the use of IVM and NCH's Free Axon software. Basically if I understand you correctly, you would like the caller to be able to phone in and select from a series of options for what he or she would like to do. And depending what the user selects, he or she is able to either leave a message or ring the phone in the office for a person to answer. Call screening is also supported by IVM when leaving voicemails so you can hear what is being said at the time the message is left (Although I don't recommend this in a doctor's office as someone may be discussing private information over the phone and that shouldn't be publicly broadcasted). In any case it's easy to setup IVM for listening to messages in different mailboxes and also having the option of sending them via email or collecting them remotely by internet or by phone if you want. Now it all depends on how you plan on interfacing with the phone system you already have. Here are your options: 1) Use a voice modem Pros: You can use your existing phone system / number, simply plug and play, install modem driver and you're ready to start receiving calls. Cons: voice modems don't have excellent quality. Voice modems can't ring the phone connected to the computer. 2) Use an FXO Adapter Pros: You can use your existing phone system / number. Works with Axon and IVM to deliver a simple yet advanced phone management system. Can ring phones connected to the axon pbx software, this can include free softphones (answered with headset connected to computer), IP or USB phones Cons: Cost is higher than voice modem, also added cost of hardware phones if you do not want a softphone 3) Move to VoIP instead of your existing phone line (what most businesses are moving towards) Pros: Depending on your provider you may be able to accept more than one incoming call at a time. Your SIP VoIP account will work flawlessly with IVM and Axon. High quality calls, delivered over your internet connection. Does not require FXO adapter, therefore cut cost. Can do everything you need. Cheaper call rates. Supports multiple phones connected to system, each with own extension (for calling internally) and can be grouped so for example all phones ring when call is external. Cons: requires reliable high-speed internet connection. Added cost of hardware phones if you do not want a softphone. You may be required to get a new phone number for your office, the good thing is most telephone companies offer a forwarding feature to forward your calls to your new VoIP number as to not disrupt your office. If you decide to keep your existing line as well as have the VoiIP line, you are paying for two monthly billed phone services.
  9. I'm not exactly sure how you plan on interfacing the mobile phone with the computer/pbx. If you can get the mobile phone to use a standard phone line connection like RJ11, you can use a Linksys FXO adapter. This will hook up your existing phone line connected to the adapter and convert it to a voip line, so any phone or softphone in the office connected to the Axon pbx system can make and take phone calls from the GSM/mobile phone line. However, it is important to note that the FXO adapter only supports 1 line. Also If you are just looking at a simple way of making free calls between offices, I recommend either 1) You have the remote office softphones connect to the central office Axon pbx system so all phones go through the same system regardless of office location, and then simply phoning the designated extension of the person you want to call 2) Use a free SIP service that allows you to call SIP numbers for free and simply have each office connect to one of these SIP accounts as an external line so calls can be made to any of the locations free.
  10. Yes, inbound and outgoing PSTN calls work perfectly fine. I have my Linksys FXO adapter connected to my Vonage line (since it doesn't allow third party clients to connect to main vonage accounts) and now I can phone from any axon-connected phone in the house. And receive calls as well. Please see my other topic (the tutorial/step-by-step instruction guide to getting 2 way answer & dial with your linksys adapter.
  11. pythonpoole

    Features

    I'm no expert, but I'll answer to the best of my ability. Direct Inward System Access YES (With NCH IVM, you can setup IVR menus and/or have access codes for both internal and external users to have access to the PBX features internally or remotely. For example, I have my system setup so you can dial an extension on axon which goes to IVM. IVM answers and asks who the person would like to call so they don't need to memorize extension numbers. I also have mine set up so I can announce things over the P/A system. This is done by connecting the server audio to my speaker system and having an extension registered with IVM that immediately sends the call to a special PA voicemail box which is set to screen the calls (allow them to play over the speakers as they are being recorded). The point is you can do whatever you want with IVM, make IVR menus to run programs, change settings, announce over a PA system, call other extensions etc. Conferance Calling YES (I believe you need NCH Quorum) Remote Access YES (Axon has a built-in web interface to configure it remotely, and by phone you can use NCH IVM Answering Attendant to do things like get remote access to your voice mail or run programs on the server computer etc.) Call Detail Records YES (Logs from Axon log all calls, but also other things so there isn't a clear interface just to look at phone calls records. IVM will record call details if people leave a message, and you can create a plugin for it to save a record of each call that comes into IVM into a database.) Music On Transfer YES (With NCH IMS on hold player) Flexible Mp3-based System YES (Same as above) Random or Linear Play YES (sane as above) Volume Control YES Volume control for playback and recording levels is given for IVM and I think IMS too) Voicemail YES (With NCH IVM) Visual Indicator for Message Waiting NO (I don't think this is supported) Stutter Dialtone for Message Waiting NO (I don't think this is supported) Voicemail to email YES (Built into NCH IVM) Voicemail Groups ? I'm not sure what you mean by this, if you mean can more than one user share the same mailbox thats fine, or if you want emails to be sent to multiple people when a message is received, thats also fine. Web Voicemail Interface YES (built into NCH IVM)
  12. pythonpoole

    SIP and Axon

    Yes, when you create an extension you've automatically created an SIP account as well. So if your using a softphone, just set the username to the extension name, the password to the extension's password and then the internal IP address of the computer with Axon on it (eg. 192.168.1.2). Then simply register the different softphones with different extensions, and then setup a dialing plan in Axon enabling you to call the different extension numbers. After thats done you should be able to phone your business partners next to you by dialing their extension number (the user name of their SIP account). If you want people from home to have access to the phone system you'll have to put in the external IP of the network.
  13. Well Axon can't do this by itself, you will need to purchase separate software such as NCH's IVM Answering Attendant which is a full featured IVR and Voice Mail system that integrates perfectly with Axon. When people call in, have the call immediately directed to IVM, this can be done a few ways, one way is to make the call ring on IVM's extension (usually 199). In IVM its a simple case of settting up different Out Going Messages and Menus for users to go through and then associate it with a particular action, whether it be transferring the call, leaving a message, storing data, asking for passcodes / or credit card numbers etc.
  14. Setup Guide for using your SPA3000 / SPA3102 FXO adapter with Axon This quick-start guide will help you setup your new Linksys/Sipura FXO adapter you have purchased for your Axon PBX phone system. At the end of this guide you will be able to make calls to your PSTN (also known as POTS) line from a phone on your Axon PBX and also receive calls from your PSTN phone line through your PBX. FIRST THINGS FIRST Thre first step is to physically setup your FXO adapter. Take a standard phone cable (RJ11) and connect it to the "Phone" port on the adapter NOTE: DO NOT PLUG THE PHONE CABLE CONNECTED TO THE "Phone" PORT INTO A WALL PHONE JACK, YOU MAY DAMAGE YOUR EQUIPMENT, AND IT WONT RING THE OTHER PHONES ON THE LINE (WITHOUT REWIRING) IF THAT IS YOUR INTENTION. THE "Phone" PORT IS FOR PHONES ONLY. Take the same RJ11 phone cable and connect the other end to any analogue / standard telephone. Take a second RJ11 phone cable and connect it to your PSTN wall phone jack, or whatever phone jack you are trying to convert to a VoIP line. Take the same RJ11 phone cable and connect the other end to the "Line" port on the FXO adapter. Take the 5v Power adapter, connect it to the FXO adapter and plug it into an active power outlet. The adapter should turn on and a green LED status light should indicate this. ACCESSING FXO ADAPTER CONFIG PAGE Next, it is time to start configuring your FXO adapter. Pick up the phone connected to the "Phone" port on the adapter and dial * * * * You will be transfered to an IVR menu. From this menu, you will need to dial 110# Write down the IP address it gives you, you will need it later for further configuration. Note: If you have changed any settings before reading this guide, it is best to reset the device to factory default settings to make sure all settings are correct. To do this, dial 73738# from the same IVR menu. Press 1 to confirm when prompted. Now open any browser on the same network as the FXO adapter and go to: http://[ADAPTER IP ADDRESS]/admin/advanced where the IP address is replaced with the one you wrote down earlier, example: http://192.168.1.30/admin/advanced If you receive a user name/password prompt, you are in bad luck. Most likely the device has been locked to a certain Voip service and you won't be able to change the settings. Try contacting the people you bought it from and see if you can obtain an unlock user/pass to access the device. Depending on the device you may either have 2 sets of tabs with the top one having "Router" and "Voice" tabs, or only 1 set of tabs that all the devices have (Info, system, SIP, ...). If you have the Router and Voice tabs, select Voice. CONFIGURING THE ADAPTER FOR USE WITH AXON 1) Click on the "Line 1" tab 2) Make sure Line Enable is set to Yes 3) Under the SIP Settings header, change the SIP port to 5070 (Try 5070 first, and only if you cannot get this setup to work, then come back and try another port number) 4) Under the Proxy and Registration header, type in the IP address of the computer with Axon installed into the "Proxy:" text box 5) Make sure use outbound proxy is set to No 6) Under subscriber information set the display name to FXS1 7) Set the User ID and Password to FXS1 as well 8) (I think this step is optional), set the Dial Plan at the bottom to "(xx.)" with no quotes. If you leave the standard dialing plan you may encounter problems dialing certain numbers on the phone especially if you do not live in a country in the North American region. The (xx.) dial plan accepts pretty much any dialed phone numbers. 9) Click on the "PSTN Line" tab 10) Make sure Line Enable is set to Yes 11) Under the SIP Settings header, set the SIP port to 5060 12) Under the Proxy and Registration header, type in the IP address of the computer with Axon installed into the "Proxy:" textbox 13) Again, make sure use outbound proxy is set to No 14) Under Subscriber information set the display name to FXO1 15) set the User ID and Password to FXO1 as well 16) Under the Dial Plans header, type in "S0<:701>" (no quotes) into the Dial Plan 1: textbox. This is very important. You can change 701 to whatever extension or group you want to ring when a PSTN call is received in Axon. If you wanted to ring extension 101, you would type S0<:101> exactly. 17) Under the VoIP-To-PSTN Gateway Setup header, set VoIP-To-PSTN Gateway Enable to Yes 18) Set VoIP Caller Auth Method to None 19) Set VoIP Caller Default DP to 2 (This step is very important! If you leave it at 1, you won't be able to dial out, you will simply hear a "tone" when dialing and you will be disconnected. Also check to make sure that the Dial Plan 2 textbox (under the one modified in step 16) is set to (xx.) 20) Under the PSTN-To-VoIP Gateway Setup header, set PSTN-To-VoIP Gateway Enable to Yes 21) Set PSTN Caller Auth Method to None 22) Set PSTN CID For VoIP CID to No (You can try with Yes, but in some cases it may prevent Axon from answering your phone calls altogether). 23) Set PSTN Caller Default DP to 1 if it is not that already 24) Under the FXO Timer Values (sec), set PSTN Answer Delay to 3 or 4 (Either should be fine. This tells the FXO adapter how long to wait before routing the call to Axon. Usually, this should be 3-4 seconds to allow time for Caller ID information to be sent. It is important to change this step! If you leave it at 16, you will have to wait many many rings before axon receives the call) 25) If you live outside North America, you may need to configure additional Regional settings for your device (See Regional tabs). For example Caller ID information is transmitted differently in different regions of the world, so if you are having trouble receiving Caller ID, it is possible that is the problem. AXON CONFIGURATION You are now done with the FXO adapter configuration. You can press "Submit All Changes" now if you wish, although it may take a few minutes after you setup Axon before it "clicks" in and registers, so I prefer to keep the window open and set up axon first before submitting. Open Axon's web configuration page. If you have created any external lines or extensions for the FXO adapter already, I suggest you delete them and just return to how your Axon was before the introduction of the adapter just because some settings you have made changes to may conflict with this setup and the guide might not indicate what those settings should be set back to. 26) Go to the Extensions tab in Axon and add a new extension with Extension ID (or User Name) FXO1 This is the extension that calls from the PSTN will come in on. When a call comes through on the PSTN line, the FXO adapter is kind of like a softphone with extension FXO1 and it will dial the Axon group/extension itself instead of acting like an "external line" 27) Set the Display Name and Password to FXO1 as well 28) Set the dialing plan to one you will use for the phones on the PBX system which you want to have access to the PSTN line 29) Save the changes, and create another extension with Extension ID (or User Name) FXS1 This extension is the extension of the phone connected to the FXO adapter, so when you call the FXS1 line the phone on the FXO adapter will ring. 30) Set the Display Name and Password to FXS1 as well 31) Save the changes, and then go to the External Line tab 32) Create a new External line for your FXO adapter like "FXO LINE" 33) Unlike the instructions from NCH, in the server address enter [iP ADDRESS OF FXO ADAPTER]:5061 For example 192.168.1.30:5061 34) For the username enter anything such as "user", it does not matter. 35) Leave the password field blank, or put any random text in it, it doesn't matter either. 36) Set the "Incoming Calls Ring On Extension or Group" to an extension of your choice. Note the extension you chose in the FXO adapter settings should override this setting, so if you are trying to figure out why the wrong phone extension rings, refer back to your SIPURA adapter settings (see step 16). 37) Optional: You can add FXS to the group (example 701) that configured the FXO adapter to ring when an incoming call comes in so that the phone connected to the FXO adapter will also ring. You can also make a seperate group like 702 with just the FXS extension in it so you can dial that phone internally from a phone which can only dial numbers and not letters. 38) If you haven't done so, now is a good time to click the "Submit all Changes" button in the Sipura SPA configuration window. Your FXO and Axon should now try and communicate with each other after this. 39) You are now DONE!!! You should now have a working PBX system where you can place calls out through any Axon connected phone through the PSTN lines and have any PSTN phone call come through your Axon SIP/VoIP system. 40) If you are seeing errors in the Axon Window / Logs, Do NOT Panic, everything is fine, trust me (see the end of this guide for more details). Now is a good time to setup your dialing plans in Axon so for example if the dialed number starts with 0 make it use the PSTN line. After configuring your dial plan, test it out on a phone connected to the PBX or the FXO adapter. Assuming all works well, now test inbound dialing. Use a mobile (cell) phone and dial the PSTN phone number and allow for a few seconds for the FXO adapter to kick in and transfer the call to Axon. You're Done! Here is my actual complete configuration settings for the FXO adapter for your reference, ignore some of the configuration I have changed in areas such as the System tab as this is not relevant. http://scorptek.org/MISC/advanced.htm Explanation to errors in the Axon window / log such as this one: 21:11:38 Register attempt for sip:user@192.168.1.30:5061 failed 21:11:38 501 Not Implemented Although this error appears, your PBX system should work perfectly. All incoming calls should go through the PBX and ring the nominated extension/group and all outgoing calls on the "FXO LINE" should be able go through on the PSTN line as well. This is the only method currently that seems to work, the way NCH explains the configuration in their instructions does not seem to work correctly, and leaving the Server blank for the external line seems to do nothing at all. With this configuration Axon is trying to register the line with the username "User" and password "Password" but can't, thus the error; however everything is fine and the FXO adapter can still handle this configuration and calls made through this "Not Implemented Line." In other words, just ignore it. Ok thats it folks, hope everything works out for you ok. It took me quite a while to figure this out and get it working and I just want to thank a couple of the users who I got help/information from: Francoz and Fredtheman
  15. Thank you everyone for your help. With the combination of the NCH SPA setup guide, a third party user guide, a little help on the forums, and experimenting, I finally got a fully working FXO adapter. I have to say that the NCH guide is not very good and does not include many of the important steps to follow in order to setup a Voip to PSTN and PSTN to Voip gateway. Therefore I have decided to create a full user guide on how to set it up for other users having problems, and I will post it shortly.
  16. I am using the 3000 (not 3102), and I was not able to import the settings configuration you provided. However, I tried to copy it over manually as best I could. After some modifications, I was finally (and still am) able to dial out on the PSTN line. However I cannot receive calls through the PBX from the PSTN line. Axon logs show no recognition of any inbound call. Below is a link to the configuration settings I have used http://scorptek.org/MISC/advanced.htm What am I supposed to do in Axon to receive calls from the FXO adapter?
  17. [ UPDATED ] The problem with my SPA3000 has been fixed and through my research, assistance and experimentation, I have produced what I call the Ultimate guide to setting up your Sipura/Linksys FXO adapter for use in Axon here: http://nch.invisionzone.com/index.php?showtopic=5091 The guide is designed for any user (novice to expert) who is looking for how to setup their SPA FXO adapter with Axon or someone who has tried to setup and is unable to get it functioning correctly.
×
×
  • Create New...