Vodia PBX

Of course it is not a big deal to add that option to the address book. However we need to think about what we should do e.g. when that contact dials a hunt group which has already a ringtone set. By default the PBX uses "internal" and "external" ringtones - depending on where the call came from. We also need to keep in mind that there is a layer on top of the phone hardware - all phones (should) sound the same no matter what manufacturer. Having the phone connect the call is a somewhat special case because of the privacy implications. It would be still possible to use the hunt group to achieve this with the current versions. There is a file ringtones.xml that can be edited (through the web interface) to hijack one of the ring tones to make the phones pick up immediately. All you have to do is use a hunt group with just one agent and select a ring tone that you then change in the ringtones.xml file. In that file you will see the entry that makes the Polycom pick up the call immediately. In the following example all you have to do is set the ringer to "ringer10" in the hunt group: <tone name="ringer10"> <vendor ua="Polycom.*">Auto Answer</vendor> ...

Ahhh. You want to essentially intercom to the phones. You can do that from an extension (permission needs to be set) e.g. by dialing *90123 (123 being the extension). Is it possible for the external ACD to call *90123 instead of 123? Then you could tell the PBX to treat that call like a call from one extension (ACD, based on its IP address) to another extension. If all calls to the phones are intercom you could as well change the polycom_all template and make them auto answer. The third possibility would be to send the call to a hunt group that uses the ringtone that you want - this can in theory include the "no dot ring at all" "tone". Though this would require that you change the template for the hunt group web page which is currently suppressing that option.

You can set different ring tones when e.g. a hunt group is being called. This depends on who is being called, not who is calling. Can you elaborate a little what the use case is for specifying what ring tone to use in the address book?

Well what did you put into the URL field? It has to be an URL.

Try https://portal.vodia.com/downloads/snomOneCstaBrowser1006.zip however keep in mind its pretty old.

Is this limited to snom phones or does it also affect other brands? Is there two-way audio after the connection?

Looks pretty much straight forward. Are you able to try out a new 64.0 build? Might just add it.

The easiest is to drag and drop the call from the web portal onto an extension. I know that this was on the list for the new portal but I am not sure if that was implemented yet. Using a star code might be another possibility, but IMHO it is not very practical because nobody will be able to remember the correct (and probably very cryptic) code.

Well this is the problem: "SIP/2.0 403 From user does not match authenticated user" - which is obviously the problem. The "From" uses 22. Try to put the username into the account field and username field - that should solve the problem.

Inbound problems are usually harder than outbound. Can you post the SIP response to the INVITE that the trunk provider sends? That might give us a clue...

I would send all calls to a specific account first - this way you can make sure that you don't have an inbound call routing problem. The if that works you can refine it and try to send it to an extension based on a prefix pattern. If not, check the log file for a clue. Does the PBX receive an INVITE? Are outbound calls working?

The called number can also be important in cases where customers have multiple numbers or when mailbox messages are being forwarded. What could be a possibility to resolve the situation for people that don't want to wait for the called number is to accept # as the signal to jump to the message.

The format should be the same - 16 bit per sample, 8 kHz mono uncompressed. Maybe it sounds better because it was recorded in a studio ...

You mean changing the volume? The PBX does not "touch" the audio itself - this should be done by the analog equipment.

Well we don't have this yet - however because it has no BLF buttons it should be relatively easy to set up even manually. We'll hav to look into this though, WiFi is definitively very cool.

Did you also port forward the RTP ports? I would turn on PCAP logging for the extension then you can see what is being send out and what is being received.

So you want to move to another agent after 10 seconds?! In that case the hunt group would indeed a better (and easier) solution.

Hmm maybe some problem with the 64.0 build - we found a few other glitches will patch that into 64.0.1 soon.

Set the number of agents per stage to 1 with a long stage duration (e.g. 60 seconds) and then turn the option "Allow multiple calls to ring agents in parallel" on.

Its the last item on the list.

You can download the QR codes from the extension list view as one of the actions:

Maybe not 100 % related, but one simple answer is to use the app. Then the caller-ID does not have to be passed trough the PSTN. The Vodia app can even pass additional information, e.g. what group was called.

Admittedly the app was made with users in mind that have only one extension. Maybe we should invest some time into the hot desking feature there, which should help handling multiple accounts (using star code should work anyway). Otherwise you can go back to the login screen and scan the QR code again.

For the Vodia app we don't even send a single QR email - because it contains sensitive information that - if leaked - can obviously be used to get access to the account. For mass mail our idea is that large organizations print the page out and hand the pieces to the right persons that then scan it from their smart phones. Sounds a little old school, but is private and easy... For ZoiPer we do send this email - at least for now. We don't have any mass email feature though.

We need to get a way from sending password in emails - actually to even give passwords to users. It is a support and security problem. In the 64 version we have added a feature that allows the bulk download of QR codes so that they can be printed out (yes, on paper) and provided to the user. In many organizations that is a easy and safe way of providing users the credentials to the user login. This is in admin mode. Also we are using the Google login feature now also in the Android app, so that the user does not have to know the password at all. It is easier to set up for the administrator than the web login because of the way the app login works - just make sure that the email address is in the extension.