Jump to content

xy3

Members
  • Content Count

    37
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About xy3

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Vodia support, can you please share that CFG and any pointers regarding FXO configuration(s)? We've got an Audiocodes MP-114. Had no problem getting FXS ports working with Vodia mini but the FXOs remain a challenge. Please share ASAP.
  2. 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" :-(
  3. Yep. Our IP address here is not static so not a good option for us. We're hoping someone at snom will provide working certificate set.
  4. We are having similar certificate issues.. but using a SoHo.. for which the alpha monocerotids release has not yet been made available (running 2011-4.3.0.5021 Linux). Can 'Pradeep' (?) or someone post or PM a certificate set that will allow this to work?? Many thanks for your kind attention.
  5. 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.
  6. Having trouble getting Skype setup here too.. but ur doc URL is now 404. Can you point to current location? Many thanks.
  7. SOLVED: The trick for us was getting that "ringtones.xml" file placed on the snom ONE build -- AND making sure there were no other registrations of extensions in question. Now working perfectly. Thanks for your help/guidance.
  8. Thanks for your reply. Excellent question, but I'm unable to inspect the 601's logs, so don't know for certain. Regarding the web interface, this is a SoHo build.. how might I load that file (=step by step for a snom newbie, pls) via the SoHo admin interface?
  9. So, we poked around and could not find a "ringtones.xml" on the snomONE SoHo build to alter. Found a 'modified for 'intercom use' file here: http://forum.snomone.com/index.php?/topic/3646-4104013-linux-intercom-not-working/ We placed it in the HTML directory, as suggested in the thread above, and re-started. (No idea how a current snomONE build (-5021) will refer out to that 'ringtones.xml' file.) Double checked that Polycom xxxxx.cfg file tells the set to use the right ring behavior in response to an "Auto Answer" in Alert-Info, as noted in many places. Still, no joy.. S
  10. Thanks! We'll give this a go today and report back.
  11. Got a pair of Polycom IP601 sets running SIP 3.1.7, snom ONE SoHo running 2011-4.3.0.5021. Had "intercom" feature working great on them with a Trixbox solution. Now really struggling to get it working on the snom ONE. The sets just ring normally when the intercom prefix is applied (*90xxx). We made sure there were no other registrations of the extensions in use, and set permissions to allow sets to 'intercom' (feature works fine on the snom sets here, incidentally.) Then, we altered standard Polycom phonexxxx.cfg files to reflect what we *think* snom ONE's INVITE message might contain
  12. Thanks. Any sense for when 4.5 will be available for SoHo?
  13. UPDATE: Resolved by adding certificate noted here: http://forum.snomone.com/index.php?/topic/3993-cannot-send-email-via-gmail-on-4203958/page__p__17173#entry17173
  14. RESOLVED: Excellent -- thanks. That worked.
×
×
  • Create New...