Vodia PBX

Oh okay, looks like that is the issue. The setting is actually from the times when the PBX had no button support as we know it today. The upgrade does not automatically migrate that old setting into a button profile. I am not sure if the phone support for that list will also be like that forever. The support for dialog-based is today as far as I can tell #1; other vendors show the list as you know it from the old snom firmware based on that information.

Hmm. Then whatever was done on the server it should still work. I guess you did already restart the phone so that if fetches the latest configuration? I assume you used the button profile on the PBX. The problem with the RFC (as many other RFC) is that most phone vendors just have one subscription per BLF key. That list subscription might be more elegant, but that is not how standards and their acceptance works.

Did you automatically provision the phone or is this a manual setup?

The 30 days trial is available for Vodia partners. Check if you qualify (partner@vodia.com) or if you know someone who is already a partner.

Not sure if a reboot will help here. The problem is that for unicast paging, the PBX somehow needs to tell the phone to pick up the phone call without actually alerting the user. There is no real SIP standard for that, and it heavily depends on the device. There are even settings (security!) that may influence the behavior, which have not much to do with what is happening on the PBX. If that is the case you should be able to see that in the log files for the phone. Anyway because of this, we have added a mechanism that connects the calls anyway I think after 3 seconds in the later versions.

That's happening if one of the phones does not automatically answer. As far as I remember that problem was later solved with a short timeout so that even if there is one road blocker the page still goes through.

We did not have the Cisco 8800 series in the lab yet; however a brief look at the datasheet looks promising. The older Cisco series were primarily built for their own phone PBX system; interoperability was obviously not a priority. Maybe this phone goes beyond it, it would be interesting to get it at least registered with the Vodia PBX and see what SIP standards are supported.

Ok, in that case I would recommend to install version 5 and then replace the executable manually with the version 4 image. The installation procedure is the same, at least for Windows.

Version 4 is not supported any more for new installations, please use version 5 for new installations.

No sorry those settings are global. If you want a blank file, create a short WAV file with digital silence in it.

Not sure if the tone comes from the PBX (it is that ding-dang-dong) or the device itself. If it is played after that they probably come from the PBX. The tones for the PBX are stored in the audio_moh folder, and the files played are dingdong.wav and dongding.wav, and page_begin.wav and page_end.wav (not sure about bi_gong1.wav and bi_gong2.wav). You can replace them with your own sounds, just make sure that you keep the same 16 kbit/s, 8 kHz mono WAV file format (length is not so important).

You can use the standard "free" on http://www.vodia.com/versions

The license that you already have is good for version 4, not for version 5. If you want to use version 5, you need a new license. You can obtain license from vodia.com.

This requires a purchased upgrade.

The thing about parking is that each call is parked on a specific orbit (the PBX will announce which orbit it was). Then with the page, the orbit can be announced and the user can pick up the call from any available phone. Holding calls does not sound like a feasible alternative to me, it will be difficult to retrieve the call.

Depending on the setting on admin level, the records are deleted after so-and-so many days, typically 14 days. That includes the call history.

That's when the manual download is much more powerful than the automatic SW update

It seems that the server does not respond to packets coming from the US. Maybe they accept only packets coming from the Deutsche Telekom network.

At this point we simply don't have that (complex) feature.

You can send me a private message in this forum.

You mean the other way, receive an email on the PBX and then send it out? That is a completely different game, as it would get us into the whole printer driver topic which is a world in its own.

Looks straightforward, but with large providers you never know... It would be awesome if you can share your login data with us (private message, change the password after done) so that we can work out the details.

Yes almost, the URL would be "mailto:mudasar321@outlook.com"

Does the Telekom offer SIP trunking now?! We have a couple in Germany in the drop down, but Deutsche Telekom is missing so far however we would love to add them.

Ok. The dial plan actually has a CMC feature that you probably want to use for this. About the CDR reporting, it is a long topic. If you build something new, I would recommend to use the JSON records which include practically everything. If you want something very simple, I would just write the CDR to a file and import it with Excel at the end of the month (more information on http://www.vodia.com/documentation/cdr doc).