Vodia PBX

snom 710 was not available when version 4.5 was released. It was added in version 5.

That is a very flexible but also difficult topic. IMHO the easiest is to just modify the template either on domain or extension level to fit the local needs.

This might be a problem with the default configuration. By default, the pickup preference is 66 67 68 69, and if yous group is not on that list, yes it will fail. Either clear that list or explicitly set it on how you want it.

Change dom_footer_v5.htm.

You can make such changes on the snom_3xx_phone.xml. The one that you edited is just the "root" file, pointing to all the other files with the details in it.

Just updated http://wiki.snomone.com/index.php?title=SNMP_Ports take a look.

I know the snom forum is unavailable right now, but that is the right place for this question...

The URI goes into the "Record Location" (Admin/General/Recording CDR). The phone settings have not much to do with this (you can for example also monitor calls that come in on a trunk and go out on a trunk). Just put there sip:192.168.1.2 (where 192.168.1.2 is the IP address if a phone that has a SIP UDP port open on port 5060). Then answer the call on that phone and listen when a monitor call comes in.

That is possible. You can use for example "sip:recording.server:5060" to send all calls for recording to that external server. See http://wiki.snomone.com/index.php?title=Record_Location or http://kiwi.pbxnsip.com/index.php/Recording.

You can edit the templates on system, domain and even extension level.

For those extensions, you should make another dial plan. Every domain can have multiple dial plans. Then you can assign the limited dial plan to the extensions that should have limited access. You may also require in a dial plan that the user has to authenticate himself with a PIN code. This way, you can still allow outbound calls if the user enters a PIN code. Also from those lobby phones, users may dial the calling card account, and from there they can make outbound calls.

Ja jetzt kann man schön sehen dass auf beiden Seiten transcoding eingeschaltet wird.

No just put them into the audio_tr directory. Essentially you are just adding the missing files in that directory. Uploading them in the web interface has no effect on this.

Transcoding ist grundsätzlich nichts gutes. Wenn aber von ulaw nach alaw übersetzt wird, gehen keine Informationen verloren und es ist auch nicht besondern CPU-intensiv. Also alles okay.

I agree. The topic of trunking between the PBX is becoming more and more interesting. The idea to send the images as well is a good idea and it would make the inter-office trunk a real feature. Fail-over between branches is an interesting idea, but will be a lot more difficult.

Hmm. Vielleicht kommt das C475 nicht mit dem Wechsel von ulaw zu alaw klar. Es gibt ein Setting "Lock codec during conversation" in den globalen Settings (Settings/SIP/Audio), das würde ich mal einschalten.

They need to be in the audio_tr directory and they need to have the names like in the audio_en directory or like mentioned above. And they need to be 8 KHz, 16 bit/sample mono WAV format.

Yes, but this is not a call forwarding. The destination comes from the field "Send call to extension" setting in the trunk (the term extension is really misleading here, "destination" would have been better).

The information is also available from the web interface (agents tab). However I just saw that the columns don't reflect the idle time yet, although the information should be there--just in the wrong column.

Send us an email or private message with your activation code and status screen of the PBX (reg_status.htm). We probably have to re-write your license.

So it seems that for voicetech.se the following settings are suitable: Remote Party/Privacy Indication: Custom Headers Request-URI: Let the system decide From: Trunk ANI To: Let the system decide P-Asserted-Identity: Based on trunk account info P-Preferred-Identity: Don't use header Remote-Party-ID: Don't use header P-Charging-Vector: Don't use header Privacy Indication: Don't use header Then you need to put your phone number into the setting Trunk ANI of the PBX.

The first thing about pictures is that they should be "thumbnail size", meaning their resolution should be around 100 x 150 pixel. Unfortunately, if you take pictures with modern cell phones, they are huge and not being displayed on the phones (http://wiki.snom.com...:Caller_Picture). In the UCClient we have added a nice drag & drop feature that does all the magic for you; however installing the UCClient for every extension is an exercise that I would not recommend right now. The LDAP on the PBX does not deal with images. So my suggestion would be to take a photo edit program of your choice, and manually process those pictures. Then you can upload them from the domain admin mode into the accounts. Sorry for the inconvenience, but that is probably the easiest way to go. Edit: P.S. why don't you just use one snom ONE then? For this installation size it should be no problem and you are already using VPN.

The Turkish recordings were made before the cell phone options were added to the code. That is probably another issue here. The following prompts are used in the cell phone menu: aa_connect_call.wav, aa_reject_call.wav, aa_voicemail_call.wav, aa_redirect_call.wav, aa_park_call.wav, aa_send_operator.wav, aa_redirect_dest.wav, aa_add_callback.wav and aa_callback_added.wav. Maybe you can use *98 to quickly record those in Turkish. Eventually, we have to record the whole set again.

Well writing to the phone display is not trivial. Alternatives could be using the web-browser when someone is monitoring the group from there, or the CSTA browser (our little tool for Windows that generates pop-up windows for incoming calls).

Da es sich bei der PBX um einen B2BUA handelt, sollte man eigentlich ausschliessen können, dass irgendwas vom C475 auf den Trunk "durchschlägt". Klappt es denn wenn das snom sich auf der Extension von dem C475 registriert? Vielleicht liegt es einfach daran, dass das C475 auf CLIP steht und deswegen der Trunk-Provider streikt.