suppa Posted March 21, 2006 Share Posted March 21, 2006 Hi! My configuration is as follows: I have Uplink 1.00, Axon 1.06 and Skype running on my computer. As SIP device, I´m using my Fritz!Box Fon 7050 in my network. The SIP device is at 192.168.0.1 and I have the extension 678 defined in Axon. The computer is at 192.168.0.20. Extension 679 in Axon is in use for Uplink. Uplink is configured to call 678 on incoming calls. It seems to work, here is what Axon says: SIP Private IP is: 192.168.0.20:5060 Unable to auto-detect public IP. Using private IP. (I've turned STUN off) SIP Public IP is: 192.168.0.20:5060 Extension 679 is at: sip:679@192.168.0.20:5070 Extension 678 is at: sip:678@192.168.0.1;uniq=6F.......... Uplink writes: SIP Private IP is: 192.168.0.20:5070 SIP Public IP is: 80.109.xxxxxx:62254 SIP Number: 679@:11776 Attempting to register sip:679@notebook Registered as: sip:679@notebook Skype is available Successfully attached to Skype Skype is available Successfully attached to Skype If I take my telephone and dial 679, then I get a connection via Skype (have tried it with echo123). The log says: Skype is calling... Skype is calling... Incoming SIP call Call has disconnected However, it works only for the first call. Also, Skype won't really hang up and Skype will freeze until I kill the Uplink process in the task manager. And, it doesn't work for incoming calls at all. If somebody tries to Skype me, then Skype and Uplink will also freeze. Might there be a problem because of the SIP public IP in Uplink? But how can I tell Uplink to work in the local network, without STUN or something. And is it normal that the Skype messages in Uplink are coming twice? Thank you for suggestions! suppa Link to comment Share on other sites More sharing options...
Triplef Posted May 16, 2006 Share Posted May 16, 2006 Do you need to have skype running for uplink to work ? if so why the program path ? im lost i see no skype dialing nowhere and tried both 2.0 and 2.5 of skype.. i do see incoming sip call but uplink doesnt show any DAMN DEBUG !!! shoudl show at least incoming call sip for XXXNNNXXXX CODERS add a debug switch please.. Hi!My configuration is as follows: I have Uplink 1.00, Axon 1.06 and Skype running on my computer. As SIP device, I´m using my Fritz!Box Fon 7050 in my network. The SIP device is at 192.168.0.1 and I have the extension 678 defined in Axon. The computer is at 192.168.0.20. Extension 679 in Axon is in use for Uplink. Uplink is configured to call 678 on incoming calls. It seems to work, here is what Axon says: SIP Private IP is: 192.168.0.20:5060 Unable to auto-detect public IP. Using private IP. (I've turned STUN off) SIP Public IP is: 192.168.0.20:5060 Extension 679 is at: sip:679@192.168.0.20:5070 Extension 678 is at: sip:678@192.168.0.1;uniq=6F.......... Uplink writes: SIP Private IP is: 192.168.0.20:5070 SIP Public IP is: 80.109.xxxxxx:62254 SIP Number: 679@:11776 Attempting to register sip:679@notebook Registered as: sip:679@notebook Skype is available Successfully attached to Skype Skype is available Successfully attached to Skype If I take my telephone and dial 679, then I get a connection via Skype (have tried it with echo123). The log says: Skype is calling... Skype is calling... Incoming SIP call Call has disconnected However, it works only for the first call. Also, Skype won't really hang up and Skype will freeze until I kill the Uplink process in the task manager. And, it doesn't work for incoming calls at all. If somebody tries to Skype me, then Skype and Uplink will also freeze. Might there be a problem because of the SIP public IP in Uplink? But how can I tell Uplink to work in the local network, without STUN or something. And is it normal that the Skype messages in Uplink are coming twice? Thank you for suggestions! suppa <{POST_SNAPBACK}> Link to comment Share on other sites More sharing options...
woodpecker Posted May 18, 2006 Share Posted May 18, 2006 I find uplink causes the skype client to freeze as well on first call via skype out, although it seems ok on skype to skype. I am using it with a asterisk@home pbx setup, I think this must be an uplink bug, anyone from NCH able to comment? Link to comment Share on other sites More sharing options...
nchBen Posted May 19, 2006 Share Posted May 19, 2006 anyone from NCH able to comment? I'm looking into this and other issues for the next release. BW Link to comment Share on other sites More sharing options...
eddylai Posted July 1, 2006 Share Posted July 1, 2006 I'd similar problem while run the uplink in WinXP. Runnig Uplink in Win2k is okay. But I still can't use it because after the incoming call sent to my SIP client, the skype will drop the line by reason "sound device problem". In fact I can hear the first few word before the line was dropped. So the problem was my Skype (2.0x & 2.5) do not like device "uplink" as its sound device. Link to comment Share on other sites More sharing options...
bennyzhou Posted August 24, 2006 Share Posted August 24, 2006 I'd similar problem while run the uplink in WinXP. Runnig Uplink in Win2k is okay. But I still can't use it because after the incoming call sent to my SIP client, the skype will drop the line by reason "sound device problem". In fact I can hear the first few word before the line was dropped. So the problem was my Skype (2.0x & 2.5) do not like device "uplink" as its sound device. tried skype 2.6 and uplink, skype froze 2.5 and uplink have no such problem Link to comment Share on other sites More sharing options...
mstelephone Posted September 11, 2006 Share Posted September 11, 2006 I believe I can successfully re-create the Skype "freezing" issue 100% of the time Skype: Version 2.5.0.137 Uplink: Version 1.1 Windows XP Home Edition: Version 2002, Service Pack 2 As mentioned in previous posts, I have only seen the issue in SkypeOut calls, not in regular Skype to Skype calls. When my VoIP endpoint makes a SIP -> SkypeOut call, it will always work if I let the SkypeOut call get connected. (ie. call recipient answers the call) BUT, if I quit (CANCEL) the call before the call is setup, then I will experience the freeze. Uplink correctly accepts the CANCEL from my VoIP endpoint, and indicates "Call has disconnected". Hence the SIP messaging [ CANCEL / 487 Request Terminated ] is correct. (observed on Ethereal) During this CANCEL state, the Skype client is showing "Connecting ..." Even though my VoIP endpoint has gracefully CANCEL the call, Skype is stuck in this state and frozen. If I kill the Uplink process via Windows Task Manager, Skype then unfreezes, shows "Cancelled" and continues to work normally after that. nchBen, are you able to confirm that you can re-create the issue in this manner ? Definitely would be sweet if this freeze issue can be addressed on the new version. Cheers. Link to comment Share on other sites More sharing options...
mstelephone Posted November 14, 2006 Share Posted November 14, 2006 Version 1.2 still had this freeze issue as I described. But Version 1.3 seems to address the issue. NOT sure though if 1.30 seems to have a new issue. It won't accept the incoming SIP calls. But if I go into Skype, and select Tools->Options->Privacy and select "Manage other programs' access to Skype", and remove UPLINK. Then when I restart Uplink, it will "re-attach" itself to Skype, and then my incoming SIP calls work fine. It is as if Skype is no longer honoring it's attachment to Uplink. Uplink screen though shows that it has successfully attached to Skype. Link to comment Share on other sites More sharing options...
nchBen Posted November 16, 2006 Share Posted November 16, 2006 I am confident that the freezing issue has been resolved across the board on all CPU architectures now. However, if anyone experiences cases of Uplink/Skype freezing - especially repeatable cases please let me know with as many details as possible. Ben Link to comment Share on other sites More sharing options...
cesar2024 Posted January 20, 2007 Share Posted January 20, 2007 Hi!My configuration is as follows: I have Uplink 1.00, Axon 1.06 and Skype running on my computer. As SIP device, I´m using my Fritz!Box Fon 7050 in my network. The SIP device is at 192.168.0.1 and I have the extension 678 defined in Axon. The computer is at 192.168.0.20. Extension 679 in Axon is in use for Uplink. Uplink is configured to call 678 on incoming calls. It seems to work, here is what Axon says: SIP Private IP is: 192.168.0.20:5060 Unable to auto-detect public IP. Using private IP. (I've turned STUN off) SIP Public IP is: 192.168.0.20:5060 Extension 679 is at: sip:679@192.168.0.20:5070 Extension 678 is at: sip:678@192.168.0.1;uniq=6F.......... Uplink writes: SIP Private IP is: 192.168.0.20:5070 SIP Public IP is: 80.109.xxxxxx:62254 SIP Number: 679@:11776 Attempting to register sip:679@notebook Registered as: sip:679@notebook Skype is available Successfully attached to Skype Skype is available Successfully attached to Skype If I take my telephone and dial 679, then I get a connection via Skype (have tried it with echo123). The log says: Skype is calling... Skype is calling... Incoming SIP call Call has disconnected However, it works only for the first call. Also, Skype won't really hang up and Skype will freeze until I kill the Uplink process in the task manager. And, it doesn't work for incoming calls at all. If somebody tries to Skype me, then Skype and Uplink will also freeze. Might there be a problem because of the SIP public IP in Uplink? But how can I tell Uplink to work in the local network, without STUN or something. And is it normal that the Skype messages in Uplink are coming twice? Thank you for suggestions! suppa do you no is work on d-link dvg 1120s y try ton config but y ave trouble so need help Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now