Pablo

From how many different ITSPs do your DIDs come from? If they all come from the same ITSP, then you should only need 1 trunk + six extensions. Then--as you did--assign each DID to the Account Number field of each extension, i.e. 40 999-888-7770 41 999-888-7771 42 999-888-7772 43 999-888-7773 44 999-888-7774 45 999-888-7775 If you want the outbound caller ID for every extension to publish the same number, simply put your "main number" in the ANI field of each extension.

I believe that you first need to test if your current license is eligible for an upgrade to version 4.5.1, here: https://snomone.com/upgradev4 Otherwise, you need to first register & go through the checkout process to obtain a license to v5, here: https://www.snomone.com/versions

Just to be sure; I logged into the extension's web portal; deleted the (i) username, (ii) password, and (iii) Exchange server address; clicked save; and logged out. I waited 15 minutes, then logged back in and entered all the relevant info., including https://m.google.com;'>https://m.google.com; but, on the PBX, still receive Activesync Status Error: Failure 2. Status = 8 The weird part, is that from my point of view, it appears that https://m.google.com is the correct Exchange server address. When I first used that address, my Google Apps domain quarantined the PBX until I approved it w/in my Google Apps domain's Mobile Settings. Within the Google Apps domain's Mobile Settings, the PBX is listed as an active sync device. When I click to read the device's details, it shows the following: Status: Approved Name: Pablo Carranza Email: pablo@pcatty.com Device ID: v140Device First Sync: 4/20/13 10:51 AM Last Sync: 4/22/13 1:20 PM OS: Unknown Type: Google Sync User Agent: Mozilla/4.0 (compatible; PBX),gzip(gfe)

That's weird. I, too, am running 5.0.8 and under the General Tab, there's an 'Administrator only' section. Below that is a 'General' section that asks for First name, Last name ... SIP password, Web password, PIN ....

Have you tried editing the button provisioning file snom_300_buttons.xml? What version of snom ONE are you using? I remember that the older versions (v4.x) had an area under Admin > Provisioning (or, PNP, perhaps) where you could manipulate the settings for 3 buttons on the snom300.

Domains > List > {select the domain} > Accounts > Extensions

What's this mean?: [5] 2013/04/22 13:58:26: Activesync: Syncing failed 1. Error code = 401 I received this 401 error code when I tried a different URL as the Exchange Server URL: https://www.google.com/m8/feeds (which I read about in this article: Google Contacts API version 3.0)

Does the PBX have an Exchange Web Services URL (Example: https://ExchangeMail.domain.com/EWS/Exchange.asmx); or the equivalent?

I realize it's an obvious ?, but are you logged in as root? Also, have you tried to simply create the directory /usr/lib; so that you can move the libstdc++.so.6 file into it? RE: not being able to access the admin page, I wonder if you might not have a problem in the routing table?

After learning that Google has decided to extend its support of ActiveSync, I tried using my Google Apps for Business account's credentials, but get the following errors: When I set the Exchange Server address to https://m.google.com, the log read: [5] 2013/04/20 10:55:01: Activesync: Start syncing. [8] 2013/04/20 10:55:01: HTTP client: Connect to 74.125.142.193:443, pending requests 0 [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: send_client_hello(03015172ba56e7 ... 652e636f6d) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: process_server_hello(030151 0000000) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] process_certificate(000 ... d57e98) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] process_server_hello_done() [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] rsa_n(da62984092 ... 3f40db94e4c5b3) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] rsa_e(010001) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Pre Master Secret(030108d ... 31254da5e) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Block Padded(000209b38cc1cd3 ... 254da5e) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Encrypted Pre Master(1029e9e7 ... 37cfa54414f) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Client Random(5172b ... 891) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Server Random(517 ... 77ba) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Master Secret(462b ... a6da5) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] send_client_key_exchange(008010 ... 54414f) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] send_change_cipher_spec(01) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] perform_change_cipher_spec(0005) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Key Block(3aa9b ... c6e22) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Client Write MAC Secret(3aa ... 1f03e) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Server Write MAC Secret(cf97 ... 06) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Client Write Key(5a8 ... a95) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] Server Write Key(9ff ... e22) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] send_finished(3ffa ... 89) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] process_change_cipher_spec(01) [9] 2013/04/20 10:55:02: HTTP 74.125.142.193:443: [630488bd] process_finished(e8c ... da5) [8] 2013/04/20 10:55:04: HTTP client: Connect to 74.125.142.193:443, pending requests 0 [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: send_client_hello(0301 ... 36f6d) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: process_server_hello(03015172b ... 0400000000) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] process_certificate(00063a0 ... 57e98) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] process_server_hello_done() [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] rsa_n(da6298 ... e4c5b3) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] rsa_e(010001) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Pre Master Secret(0301eb ... 176) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Block Padded(00025 ... 4176) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Encrypted Pre Master(63f0fa ... dfa4) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Client Random(517 ... 140) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Server Random(5172ba ... a0b) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Master Secret(e586 ... 45f8a) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] send_client_key_exchange(008 ... dfa4) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] send_change_cipher_spec(01) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] perform_change_cipher_spec(0005) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Key Block(17f64ad ... 248) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Client Write MAC Secret(17f6 ... e6) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Server Write MAC Secret(74 ... d14) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Client Write Key(50b ... d3f) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] Server Write Key(1b ... 48) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] send_finished(42 ... ee2) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] process_change_cipher_spec(01) [9] 2013/04/20 10:55:04: HTTP 74.125.142.193:443: [b9fb7216] process_finished(21 ... cb8) [5] 2013/04/20 10:55:04: Activesync Status Error: Failure 2. Status = 8 Then, when I set the Exchange Server address to http://m.google.com, the log read: [5] 2013/04/20 10:57:19: Activesync: Start syncing. [8] 2013/04/20 10:57:19: HTTP client: Connect to 74.125.142.193:80, pending requests 0 [5] 2013/04/20 10:57:19: Activesync: Syncing failed 1. Error code = 302 Finally, when I left the Exchange Server address emtpy, the log read: [5] 2013/04/20 11:09:01: Activesync: Start discovery. [8] 2013/04/20 11:09:02: HTTP client: Connect to 0.0.0.0:80, pending requests 0[5] 2013/04/20 11:09:03: Activesync: Redirection. [5] 2013/04/20 11:09:03: Activesync: Start discovery. [2] 2013/04/20 11:09:03: HTTP address is empty

Any luck?

I don't know if this sheds light on your question, but here's an excerpt from my support ticket at Vitelity, when I was trying to work through this: Given that this person thought that a snom ONE IP PBX is a "stand alone device" didn't help, either!

Does this not work anymore?: http://forum.snomone.com/index.php?/topic/5547-auto-provisioning-with-polycom/page__view__findpost__p__27082

Steve, When you say that here's your "IP registration" set-up; what do you mean by that, exactly? There're two ways to connect a trunk to Vitelity: (i) SIP Registration or (ii) IP authentication. If you're willing to tinker a little bit, you may be able to get rid of that 10-second delay by employing the workaround I described in a different forum topic (see post #12). If you follow my example, you'll want to make sure that you change the "type" variable on each trunk from "proxy" to "registration." In addition, you'll need to log into your customer portal at Vitelity and create a login ID & password for a "Sub Account" under the DIDs tab.

Now that I created two trunks (see post #12, above), instead of trying to use a combined (inbound/outbound trunk), everything is working flawlessly!

In snom ONE, the path (via the web interface) is something like Admin>Domains>{Domain xyz.com}>Trunks: Trunk 1; Trunk 2, etc. Select the trunk that the pbx uses when you call your office in ND. In there, you'll find an option for "Trunk requires out of band-DTMF tones." There's more info. on the snom ONE wiki, here: Trunk Settings

Thanks for the offer, Mr. X! But, I think I've stumbled upon the solution. snom ONE piqued my curiosity last night when he asked how many trunks to Vitelity I was using; so, instead of continuing to bang my head against the (figurative) wall, I created one inbound trunk and one outbound trunk and... (drum-role, please)... voila! Inbound trunk is using sip29.vitelity.net for the (i) Domain; (ii) Proxy Address; and (iii) Explicitly list addresses for inbound traffic; and the outbound trunk is using outbound.vitelity.net for those three settings.

Might be a DTMF problem on the trunk or phone. In the trunk, try toggling "Trunk requires out of band-DTMF tones" if the carrier doesn't state the specific setting you should use.

I only have 1 trunk (w/Direction set to: Inbound and Outbound); That's the annoying part: The log doesn't even mention that the PBX IDs the trunk; Additional settings are: Domain: sip29.vitelity.net Proxy Address: sip:outbound.vitelity.net:5060 Explicitly list addresses for inbound traffic: I've tried alternating b/w: 64.2.142.0/24 66.241.96.0/24 66.241.99.0/24 66.241.111.0/24 and (only) sip29.vitelity.net

I reviewed the instructions you suggested and I've tried these combinations (among many other!): Scenario 1: In the extension settings, set "Account number(s)" to: 45 608-371-6430 and in the trunk settings, set "Send call to extension" to: !([0-9]{10}$)!\1!t!45 Scenario 2: Account number(s): 45 608-371-6430 Send call to extension: 45 Neither worked. Any thoughts?

Flawlessly? No. I'm able to make outbound calls just fine. But, according to Vitelity, based on their trace, snom ONE does not know what to do w/the incoming calls. Here's what they sent me: Are you able to help? Please!

In its support page, Vitelity provides configuration info. for Asterisk, FreePBX, X-Lite, Linksys, Switchvox, Elastix, and, finally, Generic SIP. I'm trying to extrapolate the correct trunk settings for snom ONE from the other config examples, but I'm having trouble getting inbound calls to work. In the Generic SIP example, all the info. that Vitelity provides is the following: Under FAQs, I found: In the Switchvox config example:

Does the "Explicitly list addresses for inbound traffic:" setting accept IP address blocks; b/c, according to Vitelity, Media & SIP signalling for calls may originate from within the following IP ranges: 64.2.142.0/24 66.241.96.0/24 66.241.99.0/24 66.241.111.0/24

Just as an FYI for anyone else that may be interested... Per Vitelity Support: Ensure firewall is open for the following ranges as Media and SIP signalling for these calls may originate from within the following IP ranges: 64.2.142.0/24 66.241.96.0/24 66.241.99.0/24 66.241.111.0/24

Did you ever get this to work? Does the trunk require an ANI?