reco Posted December 26, 2012 Report Posted December 26, 2012 reboot extensions stopped working steps to reproduce 1. go to account list of a domain 2. check a select box of an extension 3. form the more actions pulldown choose reboot selected accounts -> phone is not rebooting click on registration link in account list does not open the phones ip address on our pbx it links to https://%7bx-snom-adr%7d:80 steps to reproduce 1. go to account list of a domain 2. click the link in the status column -> new window opens with address: https://%7bx-snom-adr%7d:80 Quote
Vodia PBX Posted December 26, 2012 Report Posted December 26, 2012 Obviously a bug sneaked into the phone firmware. Hopefully the next version that snom releases will fix that. Quote
reco Posted December 26, 2012 Author Report Posted December 26, 2012 Obviously a bug sneaked into the phone firmware. Hopefully the next version that snom releases will fix that. which issue are you commenting on? Quote
Vodia PBX Posted December 26, 2012 Report Posted December 26, 2012 The address that the phone delivers. Quote
reco Posted January 2, 2013 Author Report Posted January 2, 2013 what about the reboot feature? Quote
reco Posted January 2, 2013 Author Report Posted January 2, 2013 sending emails via gmail smtp stop working. turning of `Check server certs for emails` fixes the issue. was wondering if you could provide instructions how to install the attached gmail certificate. log [8] 20130102132655: SMTP: Connect to 74.125.131.109:587 [8] 20130102132655: SMTP: Received 220 mx.google.com ESMTP z20sm43460927vds.12 [8] 20130102132655: SMTP: Send EHLO server@domain.com [8] 20130102132655: SMTP: Received 250-mx.google.com at your service, [98.113.181.115] 250-SIZE 35882577 250-8BITMIME 250-STARTTLS 250 ENHANCEDSTATUSCODES [8] 20130102132655: SMTP: Send STARTTLS [8] 20130102132655: SMTP: Received 220 2.0.0 Ready to start TLS [8] 20130102132655: SMTP: Send EHLO server@domain.com [5] 20130102132655: SMTP: Connection to 74.125.131.109:587 failed mail.google.com.cer.zip Quote
Vodia PBX Posted January 2, 2013 Report Posted January 2, 2013 You need to import that certificate below as trusted root ca for server authentication. However by default the "Class 3 Public Primary Certification Authority" should be already in your list of trusted root CA if you did a fresh install. -----BEGIN CERTIFICATE----- MIICPDCCAaUCEDyRMcsf9tAbDpq40ES/Er4wDQYJKoZIhvcNAQEFBQAwXzELMAkG A1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFz cyAzIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk2 MDEyOTAwMDAwMFoXDTI4MDgwMjIzNTk1OVowXzELMAkGA1UEBhMCVVMxFzAVBgNV BAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAzIFB1YmxpYyBQcmlt YXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MIGfMA0GCSqGSIb3DQEBAQUAA4GN ADCBiQKBgQDJXFme8huKARS0EN8EQNvjV69qRUCPhAwL0TPZ2RHP7gJYHyX3KqhE BarsAx94f56TuZoAqiN91qyFomNFx3InzPRMxnVx0jnvT0Lwdd8KkMaOIG+YD/is I19wKTakyYbnsZogy1Olhec9vn2a/iRFM9x2Fe0PonFkTGUugWhFpwIDAQABMA0G CSqGSIb3DQEBBQUAA4GBABByUqkFFBkyCEHwxWsKzH4PIRnN5GfcX6kb5sroc50i 2JhucwNhkcV8sEVAbkSdjbCxlnRhLQ2pRdKkkirWmnWXbj9T/UWZYB2oK0z5XqcJ 2HUw19JlYD1n1khVdWk/kfVIC0dpImmClr7JyDiGSnoscxlIaU5rfGW/D/xwzoiQ -----END CERTIFICATE----- Quote
reco Posted January 3, 2013 Author Report Posted January 3, 2013 hi there, importing that cert does not help unfortunately these are the certs i have in there now after importing the one you posted here: Quote
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.