Jump to content
Vodia PBX forum

corona

Members
  • Content count

    16
  • Joined

  • Last visited

Everything posted by corona

  1. Hi, Seems that I am the only FreeBSD user of the Snom ONE?... Would it be possible that I can have a FreeBSD binary for the 4.5.1.1107 version? It has some fixes that I am looking for. (ie. *When matching inbound calls on trunks, the PBX does not check the presence of it's IP address any more.) In addition, would it also be possible that a PBXnSIP Win32 build could be released, too? I have another box that is still running 4.2.1.4025 (Win32) ... Its license covers the upgrade till May.31 2012. I think I can at least upgrade it to some release of 4.5.0, but I couldn't find the PBXnSIP version to download..... Thanks a lot.
  2. Hi, Looks like I am the only FreeBSD user here..... Any change for a FreeBSD version of 2011-4.5.0.1050 ? Thanks a lot.
  3. corona

    2011-4.3.0.5021 Binary?

    Thanks a lot!
  4. Hi, Just wondering if there will be a FreeBSD binary for Release 2011-4.3.0.5021? I have been waiting for like a month.. .. Thanks.
  5. corona

    Lost access to cs410

    Hi all, We have a CS410 that is used for our SIP devices' test bed. The device is on a public network and is protected with a good password. Yesterday, our engineer told me that they can't access the cs410. I figured that it does not respond to pings. Therefore, I reboot the device, but still can't ping the box. I then do a factory reset by pressing the reset button till the fxo lit up and power cycle the box. Unfortunately, I still couldn't get a ping from the box after the reset (I ping 192.168.1.99 after reset). When rebooting, the Run light will lit for about 40 seconds and then goes off afterward (even after reset). Actually, this is the second time I have seen this. The last time we have this problem (just about one years ago), I have to spend 100USD + shipping and sent back the unit for repair. I kinda feel this is just a software issue (ie. file system full?) and could be fixed without opening the box, because the box was intact last time. Thanks.
  6. corona

    Lost access to cs410

    I don't think the WAN light blinks when it is connected, but I'll check tomorrow. Only the power light stays on (if no ethernet cable connected).
  7. Hi, Could anyone help me on getting the certificate working on our Snom ONE? We bought a RapidSSL certificate for our SIP server, and I can see the server uses the new certificate in HTTPS connection right after I install the certificate. I then turn on the strict certificate verification option in our snom phone to get better security over the connection. However, the phone shows that the server does not uses the purchased certificate. Instead, it still uses self-generated certificate in the TLS connection. Could anyone shed some light for me? Attached is some information that may be helpful. TLS_Certificate_from_Server.jpg: The TLS certificate that the phone receives from the server. Certificate_Installed_on_Server.jpg: I have installed the purchased certificate as every type in the server. sip_error.txt: The error message from the phone log. sip_error.txt
  8. corona

    Different Certificate used in HTTPS and TLS?

    I can offer our login credentials if you have time to check it out. (but I can't send a PM to you though.)
  9. corona

    Different Certificate used in HTTPS and TLS?

    I just tried, but still couldn't get the certificate to work. I deleted the domain certificate first. I then installed our certificate + private key as the server certificate. I also tried to install our certificate with Equifax root CA + private key, both does not work. Snom ONE will use self-generated certificate in HTTPS connection afterward. Any ideas?...
  10. corona

    Different Certificate used in HTTPS and TLS?

    It is still easier than Calculus, IMHO..... I actually have added our certificate as the server certificate for the PBX, and I also added the certificate from Equifax Secure Certificate Authority as the root CA for both server and client. But Snome ONE still uses self-generated certificate. (I have also tried to add our certificate + Equifax certificate as the server certificate as well) I think the problem is that Snom ONE will uses self-generated certificate when the client requests a certificate using IP address. An easy way to test is to connect the server using https://ip.address/ and you can see that Snom ONE responds with self-generated certificate even if a server certificate is assigned. Could you test it? Have a nice day.
  11. corona

    Different Certificate used in HTTPS and TLS?

    Umm... this is getting more interesting now. I just figured out that, the server will use different certificates in HTTPS connection with different browsers, and only FireFox (both 3.6 and 4.0) could make the server use the correct certificate. My test result: FireFox: correct certificate used IE 8.0: self-generated certificate used Chrome 11: self-generated certificate used IE 9.0: Internet Explorer cannot display the webpage (duh!!) It seems that the Snom ONE server has different HTTPS/TLS behavior with different agents (which cause my problem). Does anyone see this as well? Server version: 2011-4.2.0.3981 (FreeBSD) License Status: snom ONE blue Edit: I added our certificate as the "Server certificate chain + private key". But when I connect to the server using its IP Address, the server still uses self-generated certificate. Is this a correct behavior?
  12. corona

    Different Certificate used in HTTPS and TLS?

    I just tried, but it still did not work..... I converted the Equifax_Secure_Certificate_Authority.cer to DER format and uploaded to the phone. I also cleaned up the certificates in the Snom One server as well, and only the purchased certificate and the Equifax_Secure_Certificate_Authority certificate were kept. I still got the same error message from the phone: [1] 8/5/2011 00:09:49: TLS: Could not verify certificate <Country: DE; State: Berlin; Locality Berlin; Organization: Snom Technology AG; Common Name: 000413440000; eMail: >. Unknown issuer <Country: DE; State: Berlin; Locality Berlin; Organization: Snom Technology AG; Common Name: snom ONE intermediate; eMail: >. [1] 8/5/2011 00:09:49: TLS: Refusing TLS connection. Invalid or unknown Certificate received From the "Common Name" field, I think the certificate got rejected by the phone is generated by the Snom ONE server? This also means the server didn't use the certificate I provided, but generated one by itself instead.
  13. Hi, I'm wondering if there is any 4.0 binaries available for FreeBSD? Or when it will be available.. Thanks.
  14. corona

    v4 Binaries for FreeBSD?

    I know.... but do you have any schedule on releasing v4 on FreeBSD?
  15. corona

    Extension got dropped frequently

    it works great. Thanks a lot.
  16. Hi, I installed pbxnsip in a FreeBSD box and use two snom300 to do a small trial. However, I keep seeing registered extensions got dropped frequently. Is there any settings I have to adjust in pbxnsip or snom? Here is the sip log I got. Thanks a lot. [5] 20090527184319: SIP port accept from 172.110.0.156:4357 [7] 20090527184319: SIP Rx tls:172.110.0.156:4357: REGISTER sip:SIP.AAA.COM.TW SIP/2.0 Via: SIP/2.0/TLS 172.110.0.156:4357;branch=z9hG4bK-bq8x0dzk8dk4;rport From: "711" <sip:711@SIP.AAA.COM.TW>;tag=q53dvjkfmo To: "711" <sip:711@SIP.AAA.COM.TW> Call-ID: 3c273098f32d-90293snf3ceu CSeq: 4917 REGISTER Max-Forwards: 70 Contact: <sip:711@172.110.0.156:4357;transport=tls;line=yra73fxq>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:2863965b-e672-4b52-9c94-a7f53bfefa30>" User-Agent: snom300/7.3.14 Supported: gruu Allow-Events: dialog X-Real-IP: 172.110.0.156 WWW-Contact: <http://172.110.0.156:80> WWW-Contact: <https://172.110.0.156:443> Proxy-Require: buttons Expires: 3600 Content-Length: 0 [7] 20090527184319: SIP Tx tls:172.110.0.156:4357: SIP/2.0 401 Authentication Required Via: SIP/2.0/TLS 172.110.0.156:4357;branch=z9hG4bK-bq8x0dzk8dk4;rport=4357 From: "711" <sip:711@SIP.AAA.COM.TW>;tag=q53dvjkfmo To: "711" <sip:711@SIP.AAA.COM.TW>;tag=e642085ba4 Call-ID: 3c273098f32d-90293snf3ceu CSeq: 4917 REGISTER User-Agent: pbxnsip-PBX/3.3.1.3177 WWW-Authenticate: Digest realm="SIP.AAA.COM.TW",nonce="c0a4bec37f25e4a216bd3c960d89f77a",domain="sip:SIP.AAA.COM.TW",algorithm=MD5 Content-Length: 0 [7] 20090527184319: SIP Rx tls:172.110.0.156:4357: REGISTER sip:SIP.AAA.COM.TW SIP/2.0 Via: SIP/2.0/TLS 172.110.0.156:4357;branch=z9hG4bK-54zndw569roy;rport From: "711" <sip:711@SIP.AAA.COM.TW>;tag=q53dvjkfmo To: "711" <sip:711@SIP.AAA.COM.TW> Call-ID: 3c273098f32d-90293snf3ceu CSeq: 4918 REGISTER Max-Forwards: 70 Contact: <sip:711@172.110.0.156:4357;transport=tls;line=yra73fxq>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:2863965b-e672-4b52-9c94-a7f53bfefa30>" User-Agent: snom300/7.3.14 Supported: gruu Allow-Events: dialog X-Real-IP: 172.110.0.156 WWW-Contact: <http://172.110.0.156:80> WWW-Contact: <https://172.110.0.156:443> Authorization: Digest username="711",realm="SIP.AAA.COM.TW",nonce="c0a4bec37f25e4a216bd3c960d89f77a",uri="sip:SIP.AAA.COM.TW",response="82c44588ec45e7846157d31b662670ed",algorithm=MD5 Proxy-Require: buttons Expires: 3600 Content-Length: 0 [7] 20090527184319: SIP Tx tls:172.110.0.156:4357: SIP/2.0 200 Ok Via: SIP/2.0/TLS 172.110.0.156:4357;branch=z9hG4bK-54zndw569roy;rport=4357 From: "711" <sip:711@SIP.AAA.COM.TW>;tag=q53dvjkfmo To: "711" <sip:711@SIP.AAA.COM.TW>;tag=e642085ba4 Call-ID: 3c273098f32d-90293snf3ceu CSeq: 4918 REGISTER Contact: <sip:711@172.110.0.156:4357;transport=tls;line=yra73fxq>;expires=181 Date: Wed, 27 May 2009 10:43:19 GMT Content-Length: 0 [5] 20090527184419: Registration 3c273098f32d-90293snf3ceu closed connection, removing it
×