Vodia PBX

Yes. You have to register first, then you can get one (or more) snom ONE free from there. You can also try other features out for 30 days free of charge.

If the box gets generally non responsive (no SSH) then we can rule out problems with the PBX software. I would also check if even ping does not work any more. It might be that you just got a "bad" device, and a hardware replacement does sound like a option.

Yea no problem there. It is just about time and what to do next. It is sometimes just about winning deals that sets the priorities.

When you access it through the web browser, make sure that you include the /prov behind the server name. Also, and probably much easier, you can just take a look into the "generated" folder what the PBX has generated for the phone without the need to tweak your browser...

Yes, that's the bottom line.

First of all, when the cell phone is turned off, the mailbox probably picks up a lot of traffic. If that if not the case, another traffic source is the initial dialog with the user "press 1 to connect the call, press 2 to ..."--even if the call does not get connected that way. For the carrier, it does connect. The only workaround for that would be that the carrier tells the PBX through a SIP code or something that the handset has picked up the call, not the mailbox. But AFAIK no carrier is able to do that (or willing to do that :-P).

That is not looking good. The way the device needs to be provisioned is causing us major headaches. At this point, this device needs to be manually configured. Also it does not support buttons like the other snom devices, which makes it difficult to offer all features across all devices.

We are making progress, but this is not the final result. Actually, Grandstream is not even in the pnp.xml; we need to get some of those devices, start the integration and then add them to the documentation.

Okay, we'll just add the RTP port begin and end to the trunk. Default will be like it is right now, so there should be no backward compatibility problems.

We need to test this here.

Follow-RTP has to do with the fact that in theory according to the IETF you can send from A on system X to port B on system Y, and receive on port C on system X from port D on system Y. That has only very little practical relevance today as it is very NAT unfriendly. The port range is a global setting, independent from trunks, extensions and others. This is the first time that I hear that a trunk provider requires specific RTP ports (this is also very NAT unfriendly). There is no negotiation for RTP ports in SDP, because each side has independent ports and each side just picks one. Although theoretically possible, I would give this a low probability. If the problem can be reproduced easily, I would take a look at the PCAP trace.

Well, that is a "classic problem" and the reason why we changed the trunk header representation from version 4.3 to 4.5. In version 5, we even support the "In-Reply-To" header which was, believe it or not, already specified in the year 2002 by the IETF for this purpose (but the industry support for this header is pretty weak so far). 3xx headers are not the answer because then the call will not be on the PBX anymore. You would completely loose the cell phone functionality (e.g. when the cell phone is turned off, you always go to the cell phone mailbox) and also other functions that make a PBX valuable get lost (call recording, barge in, transfer, and others).

If you want to queue up callers, the easiest is to is ACD -- even if there is only one agent in the ACD. In the ACD, you can record such prompts. Also, you can disable call waiting on the PBX. This has the effect that the PBX does not attempt to route calls to an extension, instead performs the redirect on busy action. For example, you can redirect the caller into the ACD so when the extension becomes available again, you can then connect the call.

Understood... Multiple extensions are one way to go. However consider multiple outbound trunks as well, as they simplify the setup for the user.

Guys keep on bashing. We don't expect any support for fixing things that were not sustainable.

Lets talk about this on the phone.

Hi Vance, yes, when version 6 comes out, you will have the option to purchase an upgrade from version 5 to version 6 as well. Check out what is going on in the rest of the software industry... I would recommend to join the subscription model, as most of the hosted providers do. Then you don't have to put a lot of cash on the table and your cost scales with your revenues. This is a good partnership as we have the same interest like you have--grow your revenues.

Problem to present a friendly area code: So you have a trunk for every area code, for example from your service provider? Then this can be done with the dial plan: trunk=area123, pattern=123*, replacement=123*; trunk=area456, pattern=456*, replacement=456*; and so on. If you want to use the same ITSP line, you might still be able to set up several trunks for that same ITSP. For gateway trunks that should be very simple. Then you can set the headers to whatever your provider needs to see in the From/PAI/RPI-headers. Important is to mark them as outbound only, so that they don't accidentally pick up any inbound traffic. Shift idle time: For the idle, the PBX currently measures how long the agent is talking and how long the agent is holding. On the other hand, the data how long the agent was logged in for the day is also available. From that, the idle time could be calculated by subtracting the availability time with the talking time. Question here is how to handle hold time. If the agent is talking to some else for consultation, this is not the same like the agent taking a smoke break in front of the building. But I agree, the idle percentage would be an interesting number. P.S. Better to post two separate topics, so that answers don't get mixed up.

This is caused when one thread is trying to read something that another thread has already closed. While it does not win the beauty price, it is at this point okay.

So did you set "Add to the address book and keep it for..." to something like 1 day or more? Then you should see that the address book entry gets updated when the call connects.

Yes I believe that should work. Do you see the callers in the address book, with their CMC? Also, the adrbook entry should show the agent (you might have to verify that in the file system as it is not visible on the web interface I believe). Try again with a scenario where all agents are talking and someone with a agent preference is waiting in the ACD, then have that agent become available. Also, did you set "Caller priority" to "Try to pull out callers when their last agent becomes available"?

Right now it is not integrated. Of course you can add the file manually to the tftp directory in order to get things done. The challenge with DECT is that the user is associated with a IPEI, not a MAC address. For a seamless DECT provisioning, we would have to change that. This would also be important for other DECT devices, e.g. Gigaset or snom.

Well, you need a history in the ACD for that. Then the PBX should walk through the list of waiting callers and pick those out who could get connected to the agent that just became available. The setting is not a guarantee that the caller always gets to the same agent. Think about cases where the agent already went home. Also it is a little difficult to test as you really need people waiting in the ACD to see the effect.

This can only be a workaround. I believe a better way is to modify the snom_3xx_phone.xml only for the affected extensions (templates can be modified on domain and extension level). This has the disadvantage that future upgrades will not be merges with the personal changes that you perform.

The snom ONE mini is running a standard Debian distribution for ARM. This is good news, because there is plenty of information and manuals available e.g. from debian.org. USB memory sticks are automatically detected by the system. After you login, you should see /media/usb; there you can make your backup. root@mini's password: Linux snomonemini 2.6.33.6 #4 PREEMPT Thu Dec 8 03:18:43 EST 2011 armv5tel The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Wed Dec 12 00:47:39 2012 from surface.hq.snomone.com root@snomonemini:~# ls -al /media/usb lrwxrwxrwx 1 root root 4 May 2 2012 /media/usb -> usb0 root@snomonemini:~# ls -al /media/usb0 total 28 drwxr-xr-x 5 root root 4096 Nov 5 12:36 . drwxr-xr-x 10 root root 736 Jan 1 1970 .. drwx------ 2 root root 16384 Nov 4 01:30 lost+found root@snomonemini:~# cd /usr/local/ root@snomonemini:/usr/local# tar cvfz /media/usb0/backup130109.tgz snomONE If you want to restore the backup you have to use the command tar xvfz /media/usb0/backup130109.tgz (working directory /usr/local). This is not only interesting for disaster recovery, this is also interesting if you want to try things out with a safe way back.