Jump to content

sandun

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by sandun

  1. On the computer where I have installed Axon, I have two network interfaces, one ethernet for internet access with an adsl router (ip dinamic), and one related to Hamachi.

     

    When Axon starts always choose the public ip address related to Hamachi (5.x.x.x) and so does not work with the external sip provider.

     

    How can I force Axon to use the other network connection without disabling Hamachi?

     

    Thanks you very much for your help

    Sergio

     

    I (and others) have come across the same problem - the latest version of Axon does not fix the issue. (Asterisk @ Home seems to be OK with multiple network adapters though). Here is the related thread:

     

    http://nch.invisionzone.com/index.php?showtopic=5497

  2. Hi,

     

    Is it possible to use IPKall (www.ipkall.com, a DID provider) with Axon. The easy way to setup is to use a third party VOIP provider such as FreeWorldDialup. That is,

     

    IPKall -> FWD -> Axon (at home, dyndns hostname).

     

    However, can IPKall be set up to call Axon directly, eg:

     

    IPKall -> Axon (at home, dyndns hostname). (this is apparently possible with Asterix).

     

    I am able to connect to Axon from outside my home via dyndns. E.g. ExpressTalk (sip:extnumber@myname.dydns.org) > Axon (at home) works.

     

    Thanks.

  3. O.K, I found the problem was due my PC having multiple network connections.

     

    My server has:

    (1) Local Network (i.e. tied to the ethernet card -> router->modem->WAN)

    (2) VPN (Hamachi VPN)

     

    In Windows ControlPanel->NetworkSettings->Advanced, the connection order is set use the local network adapter(nic) first, followed by VPN.

     

    Axon (same goes to Uplink) shows the following in the console:

     

    private ip <192.168.1.x:5060>

    public ip <WAN_IP:5060>

    public ip <VPN_IP:5060>

     

    Axon uses the 'last bound ip' - i.e. the VPN IP. Hence my service provider (Pennytel) cannot locate me with that VPN IP. If I disable the VPN connection, then Axon uses the WAN IP and everything works. Re-enable VPN and Axon switches to using the VPN IP as the public IP.

     

    Why is Axon (and Uplink) using the IP from the second (last) network adapter from the list of available adapters provided by windows? Seems like a bug.

  4. Hi,

    I am newb wrt VOIP and Axon. I have setup Axon v1.09 on a Win XP machine.

     

    I have also set an up external line to a VOIP provider (Pennytel). From an extension (either ATA or Softphone/ExpressTalk), I can make out going calls via the Pennytel external line. (Uplink/Skype set up also works well).

     

    The problem is, I can not receive any calls from Pennytel i.e. another Pennytel user can not call me. I get a pennytel message saying that person is not available.

     

    How ever, (after shutting down Axon), if I set up two different softphones (e.g. ExpressTalk and XTen) on the same machine linked to two Pennytel accounts (one being the same as the Axon external line account and the second is test account), I can make and receive calls between the two.

     

    Any ideas why Axon cannot receive calls from the external line? (the console says "registered as sip xxxx@pennytel.com" - good, and the Axon public ip is correct.)

     

     

    Thanks.

×
×
  • Create New...