cmrabet Posted July 12, 2011 Report Share Posted July 12, 2011 A long day with the SkyPe support department and there is no way to make this to work. Ports 5060, and 8000-8010 opened at the router side. At the PBX side I've changed the RTP ports to 8000 to 8010 as requested by them, and restarted the service. I created SIP register trunk with my user account and so, and it registers correctly. However when placing calls we just get a busy tone...looking at the log I see PBXnSIP is using SIP TLS 5061 port....Skype guys claim their service is not compatible with TLS... So I don't know what else to do.. Quote Link to comment Share on other sites More sharing options...
Vodia support Posted July 12, 2011 Report Share Posted July 12, 2011 Please refer to the link. It will out-line how to configure your Skype trunk. Lets us know how it goes. http://plugvoip.com/SkypeTrunk.docx Quote Link to comment Share on other sites More sharing options...
cmrabet Posted July 13, 2011 Author Report Share Posted July 13, 2011 Please refer to the link. It will out-line how to configure your Skype trunk. Lets us know how it goes. http://plugvoip.com/SkypeTrunk.docx Thanks for the document but we don't have those options. Our PBX version is 3.0.1.3023 (Linux), with a license for 10 extensions. I'm not sure if we can upgrade it to the same version as the one shown on your document. I fixed the issue anyway, I had to set the RTP port from 8000 to 8010, and then in the trunk, set the "Assume that call comes from user" to the Skype Connect user account number, since it seems that without this parameter, the user sent to Skype is the extension one, and therefore FORBIDDEN from Skype. In my case, placing calls from extension 101, was doing 101@skype which was rejected. Thanks. Quote Link to comment Share on other sites More sharing options...
Vodia support Posted July 13, 2011 Report Share Posted July 13, 2011 Forgot to mention that this was tested with the latest snomONE. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 13, 2011 Report Share Posted July 13, 2011 Make sure you import the certificate that you need for Skype TLS: http://forum.snomone.com/index.php?/topic/4738-problem-with-skype-sip-connection/ Quote Link to comment Share on other sites More sharing options...
Harlow Tech Posted December 29, 2011 Report Share Posted December 29, 2011 Does anyone have this document any more? I can not seem to get Skype Connect to work and was hoping to review this but it is now 404. Daniel Quote Link to comment Share on other sites More sharing options...
Vodia support Posted January 4, 2012 Report Share Posted January 4, 2012 Please review this attachd article on how to configure skype and snomONE after you have configure the trunk follow the steps above concering the skype certificate. SkypeTrunk.pdf Quote Link to comment Share on other sites More sharing options...
xy3 Posted January 21, 2012 Report Share Posted January 21, 2012 Having trouble getting Skype setup here too.. but ur doc URL is now 404. Can you point to current location? Many thanks. Quote Link to comment Share on other sites More sharing options...
xy3 Posted January 21, 2012 Report Share Posted January 21, 2012 Get annoying "[#10171] You do not have permission to view this attachment." trying to download. Could someone PM me or open that up so others can view the doc? Many thanks. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 21, 2012 Report Share Posted January 21, 2012 Skype: Most probably a problem with the certificate chain. If you are on 4.5, rename your certs directory and restart the PBX service. Quote Link to comment Share on other sites More sharing options...
xy3 Posted January 22, 2012 Report Share Posted January 22, 2012 Yep sounds like a cert issue to us too. Trouble is we're on a SoHo, and since no one has yet set the 'update' path for SoHo users to the new 4.5 build, we're still out here running '2011-4.3.0.5021'. Tried renaming that directory and restarting just for the hell of it.. but the newly created certs with 4.3.0 don't appear to help. Certifcates soon show: "VeriSign Class 3 Secure Server CA - G3 Rejected Root CA for server authentication" :-( Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 24, 2012 Report Share Posted January 24, 2012 Looks like that is not in the default list. You can import it with copy & paste from here: http://www.certificat-ssl.eu/FAQ/en/565.html. Use the BEGIN CERTIFICATE and END CERTIFICATE version... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.