Jump to content

fulpan

Members
  • Posts

    1
  • Joined

  • Last visited

Posts posted by fulpan

  1. Hello NCH,

     

    I've had no problems so far with ExpressTalk and Axon working together.  I was even more pleased to see uplink released.

     

    I got Uplink installed with the latest version of Skype and now Uplink has some major problems. 

     

    The Axon pbx 1.06 is at 192.168.0.5:5061

    The extension number 102 is set aside for calls from SIP to Skype and back.

     

    I get the following in the log (had to manual transcribe this log too!):

     

    LINE 1 TIME  Uplink Skype2Sip started.

    LINE 2 TIME SIP Private IP is: 192.168.0.5:5072

    LINE 3 TIME SIP Public IP is: 210.195.112.137:5072

    LINE 3 TIME SIP Number is: 102@:53248

    LINE 4 TIME Attempting to register sip: 102@192.168.0.5:5061

    LINE 5 TIME Unable to find address of server: 192.168.0.5:5061

    LINE 6 TIME Unable to find address of server: 192.168.0.5:5061

    LINE 7 TIME Server 192.168.0.5:5061 did not respond to register(sip:102@192.168.0.5:5061)

    LINE 8 TIME Check server details for that line

     

    The settings on the SIP tab in Uplink is:

    Full ' friendly' display name = Skype

    SIP account number (or user) = 102

    Server (SIP proxy or virtual PBX) = 192.168.0.5:5061

    Password = test

     

    Skype is installed correctly and Uplink has changed the corresponding Audio In and Out in Skype to Uplink.  The driver installed by Skype appears to have installed correctly.  But whenever Uplink is running I can't accept or make calls from Skype without killing Uplink in Task Manager.  When I kill the Uplink process Skype works again.

     

    So there are 2 problems:

     

    1) Uplink can't seem to recognise an Axon pbx or there is an error in Uplink in line 3 of the log above.

     

    2) when uplink is running Skype becomes unusable and freezes until I kill the Uplink process in Task Manager where Skype then works again.

     

    Cheers,

    -

     

    Fabian

     

    Had same problem, after switching over to the standard port (5060) everything started working okay. You may give it a shot. Change your Axon server to run on port 5060.

     

    Server (SIP proxy or virtual PBX) = 192.168.0.5

     

    Hope it helps.

×
×
  • Create New...