Jump to content


  • Posts

  • Joined

  • Last visited

fredtheman's Achievements


Member (3/7)



  1. You want to start a business as a VoIP provider... with Axon? You gotta be kidding... Get yourself a bunch of Linux servers, and try some serious software like SER, sipXPBX, or Asterisk. For obvious security reasons, SIP servers should be in the public part of the network, or in a DMZ. Besides, it's one less headache if the server isn't itself NATed.
  2. I have 1.09 running on W2003 Server, and sometimes, clients can no longer register (Error 408). No idea why.
  3. Most likely, Asterisk can be configured to do this (extracting information from the called number and ringing a given extension), but Axon doesn't do this, and since it's closed-source...
  4. Unless I'm mistaken, bandwidth can be lower than this with more efficient codecs (G729a?), but those are typically commercial and not available by default.
  5. PBX's can't work with voice modems unless they have a driver for them that can convert analog voice into SIP messages. Unless I'm mistaken, there's no PCI FXO card available for PBX's other than Asterisk, so you're left with getting a box device. I can recommend the Linksys 3102, but there are a few brands out there. http://www.voip-info.org/wiki/
  6. Hi Do you also experience this with Axon 1.09? After a couple of days, clients that connect through the Net can no longer register with Axon. It could be the NAT firewall in front of the LAN where Axon sits, but since I mapped UDP 5060 on the firewall and registration resumes OK after I restart Axon, I suspect it's a bug in Axon. For those with remote users, have you seen this too? If yes, do you know of a good, free watchdog program that could restart Axon every night? Thanks.
  7. fredtheman

    Port issues

    If they're behind NAT firewalls, make sure the remote clients use a STUN server so that their public address is used in SIP messages. If that doesn't solve the issue, you might have to force their use of specific ports for RTP, and configure your router/firewall to map those ports to the clients. Fred.
  8. You are using hardphones, and you tried moving them to a DMZ so as to rule out the NAT firewall from the picture (ie. phones and the Axon server are both directly accessible from the Net with no NAT in between), but calls still fail at some point. So I would guess that Axon is the culprit. FWIW, here's what I observe using 1.09: - sometimes, clients that are located behind a NAT can no longer register to Axon accross the Net - sometimes, Axon no longer reports incoming calls that are routed by a Linksys SIP gateway. In both cases, restarting Axon solves the issue. That doesn't definitely confirm that Axon has a bug there, but as a test, you could restart Axon every hour or so, and see if calls no longer go quiet.
  9. If the two sites use private addresses and you go through the Net without a VPN tunnel, make sure the two applications use STUN to translate their private address into the public one, and make sure your routers/firewalls either can open RTP ports dynamically or they are set up to map the right ports to the apps.
  10. http://forums.whirlpool.net.au/forum-threads.cfm?f=107
  11. Hello I use those two pieces of technology, and I need to rewrite caller ID information on the fly: Some customers don't have names that are descriptive enough in their Name section of CID (eg. "Mc Donald's"), so I would need to... 1. look up the CID number in a database 2. fetch the city this customer is located 3. rewrite the CID Name from "McDonald's" to "McDonald's 78th St" 4. Have this SIP packet be sent to either the Axon PBX software, or to all the clients that are part of the ring group. Does anyone have an idea how I could do that, either on the Linksys or the Axon side? Unfortunately, Axon is a closed-source software, so I can't really do much on that end. I was thinking maybe of having some kind of proxy that would parse and rewrite data between the Linksys and the Axon. What do you think? Thank you.
  12. No idea, but I was looking for another free PBX for Windows and never heard of 3CX. Looks very good. I'll give it a shot.
  13. Found a work-around: Just install a copy of a softphone like X-Lite, make that a member of the 701 ring group, and configure the softphone to forward all incoming calls to a remote VoIP account. Not a good solution if you have several users who all want to be reachable on their cellphone, but it solves the issue for one-two users... until Axon allows adding foreign VoIP accounts to a ring group.
  14. Hello I noticed that NCH put out a new software called Carousel, but I don't understand what it does. It seems to stand between an SIP gateway to handle incoming PSTN calls, and then route them to Axon, but I don't understand what it does that Axon doesn't already do. Anybody knows? Cheers.
  15. Thanks for the link. It's also available at http://www.sipcpe.com/fx300GSM.html for $350 retail.
  • Create New...