xy3

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.

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" :-(

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.

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.

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.

Having trouble getting Skype setup here too.. but ur doc URL is now 404. Can you point to current location? Many thanks.

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.

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?

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.. Sets just ring away like normal. Suggestions?

Thanks! We'll give this a go today and report back.

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 regarding alerting on an intercom call, e.g.: <alertInfo voIpProt.SIP.alertInfo.2.value="intercom" voIpProt.SIP.alertInfo.2.class="4" /> Also tried "answer-after" as a value. No joy. Ideas? Suggestions? Start drinking? (kidding) Any thoughts appreciated.

We'd LOVE to see this available for SoHo!

Thanks. Any sense for when 4.5 will be available for SoHo?

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

RESOLVED: Excellent -- thanks. That worked.

We have a new snom ONE SoHo running 5021, and Polycom 601 running SIP 3.17. Most sets are snom but we have one Polycom 601 which must work; understood the SoHo would support up to three non-snom sets. We got the Polycom set to register ok, and can make incoming and outgoing calls as expected, but can't get transfer or call park to work. When pressing transfer caller is put on hold and dialtone is heard as expected, but when the target destination is dialed and transfer pressed again, the caller on hold is DROPPED and a simple call from transferee to target destination placed. Can't seem to get call park to work either. Suggestions? Workaround? We MUST be able to 'transfer' ca call from this set to another.. Please help!

SOLVED: 'Outbound proxy' under 'identity' tab for the active identity had to be valued with SoHo IP address (it had been blank). - xy3

Looking at 'function key's tab of 870 UI, that key just shows type = key event, number = retrieve. Tried clearing settings and downloaded 8.4.32. Same result; '8200 not found' when pressing they hard key. Works fine when I dial 8200 (or 200) from the keypad. Think you're onto something about http vs SIP; can you be a little more specific about what I should check in the 870's config? Also, where is 8.4.34 f/w? I did not spot it. Many thanks for your attention.

So, any ideas? Suggestions we can try??

Yes; the value was '8'. As noted, oddly, dialing '8200' from the set's keypad works fine. Pressing the 'Message' key fails every time, as described. Here's a SIP trace following a couple of 'Message' key presses: Sent to udp:192.168.0.100:5060 at 12/12/2011 12:11:00:701 (477 bytes): SUBSCRIBE sip:192.168.0.100:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.0.5:3072;branch=z9hG4bK-b2jo2mcjmruq;rport From: <sip:200@192.168.0.100>;tag=fmwxu9y0r9 To: <sip:300@192.168.0.100;user=phone>;tag=5ec0582220 Call-ID: f9ee283c919f-gw0mdp1y1fug CSeq: 736 SUBSCRIBE Max-Forwards: 70 Contact: <sip:200@192.168.0.5:3072;line=q9ppce6b>;reg-id=1 Event: dialog Accept: application/dialog-info+xml User-Agent: snom870/8.4.33 Expires: 3600 Content-Length: 0 Received from udp:192.168.0.100:5060 at 12/12/2011 12:11:00:709 (332 bytes): SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.0.5:3072;branch=z9hG4bK-b2jo2mcjmruq;rport=3072 From: <sip:200@192.168.0.100>;tag=fmwxu9y0r9 To: <sip:300@192.168.0.100;user=phone>;tag=5ec0582220 Call-ID: f9ee283c919f-gw0mdp1y1fug CSeq: 736 SUBSCRIBE Contact: <sip:192.168.0.100:5060;transport=udp> Expires: 359 Content-Length: 0 Sent to udp:192.168.0.100:5060 at 12/12/2011 12:11:26:402 (693 bytes): REGISTER sip:192.168.0.100 SIP/2.0 Via: SIP/2.0/UDP 192.168.0.5:3072;branch=z9hG4bK-eu1trzpapx3h;rport From: <sip:201@192.168.0.100>;tag=arn7wezmoe To: <sip:201@192.168.0.100> Call-ID: 2b70263c1ee5-pi9jlsjsjs67 CSeq: 3652 REGISTER Max-Forwards: 70 Contact: <sip:201@192.168.0.5:3072;line=907rdkpu>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:d928a5d1-e017-44c8-8f44-000413410439>";audio;mobility="fixed";duplex="full";description="snom870";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO" User-Agent: snom870/8.4.33 Allow-Events: dialog X-Real-IP: 192.168.0.5 Supported: path, gruu Expires: 3600 Content-Length: 0 Received from udp:192.168.0.100:5060 at 12/12/2011 12:11:26:415 (338 bytes): SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.0.5:3072;branch=z9hG4bK-eu1trzpapx3h;rport=3072 From: <sip:201@192.168.0.100>;tag=arn7wezmoe To: <sip:201@192.168.0.100>;tag=c80f3ed558 Call-ID: 2b70263c1ee5-pi9jlsjsjs67 CSeq: 3652 REGISTER Contact: <sip:201@192.168.0.5:3072;line=907rdkpu>;expires=360 Supported: path Content-Length: 0

Newbie setting up snom ONE SoHo and struggling with the 'Message' key on an 870 set. Pressing the lit key after a message is left gives only a momentary '8200 calling' on the display, then almost immediately '8200 NOT FOUND', and a couple of seconds of fast busy tome (reorder). Suspect it's something dumb that we did.. but can't figure out what. The 870 is running 8.4.33 and Soho is running 4.3.0.5021. Note we have snom Vision in use, so keeping 870 f/w at 8.4.32 or .33 is important for sensible BLF/LED behavior. Active identity of the set is extension 200. I don't see anything in a SIP trace after pressing the message key. Dialing "8200" via the keypad does bring us to voicemail without problem (as will dialing 200 from the same extension, or dialing the *97 access code). But the 'message' hard key fails (as described above) every time. Suggestions? Ideas? Workarounds??

=SOLVED VIA CURRENT (DEC 5 2011) SOHO UPDATE. WORKS LIKE A CHARM!

IT WORKS!! IT WORKS !! Fabulous. Perfect. We love you! THANK YOU!!

Found and installed an older 'SSH Secure Shell' tool, which PBXNSIP folk appear to have made use of in past, and seems to run fine. Now struggling to establish SSH session with our SoHo.. What is correct port? Username = root? Password = ??? Just a *little* bit of help would get us going. HELP!

Found and installed an older 'SSH Secure Shell' tool the PBXNSIP folk appear to have made use of. Appears to run on Win7 box okay. Struggling to establish SSH session with our SoHo.. What is correct port? Username = root? Password = ??? Just a little bit of help would get us going. Please reply!