Vodia PBX

The amount of memory is not important. The CPU usage is as the PBX needs to decompress the data, then mix both channels and finally compress it again then write it to the file system. Check the status screen of the PBX. If you see the load not more than 25 % you are in a good shape.

This can only work if the destination system believes that the call comes from an extension. So what you can try: Set up a new trunk on the source system which is outbound only and that uses the credentials of an extension on the destination system. Having the trunk outbound only makes sure we are not screwing anything up on inbound traffic on the PBX. Choose a reasonably long extension name like "2127654321" so that the chance of mixing that number up is pretty low. Create that extension with the same password on the destination system. Assign 8xxx as the pattern in the source system dial plan and use that new trunk. Give it a shot!

I would try using a good headset. It is amazing how much hardware quality matters for audio.

Not yet. But at least we now have an understanding on how it should work

1.3.6.1.4.1.25060.1.1 Call Legs Yes Calls 1.3.6.1.4.1.25060.1.2 Registrations Yes Registrations 1.3.6.1.4.1.25060.1.3 Messages Yes Minutes 1.3.6.1.4.1.25060.1.4 Call Attempts No Calls 1.3.6.1.4.1.25060.1.5 Successful Calls No Calls 1.3.6.1.4.1.25060.1.6 Media CPU load Yes Value 0..100 1.3.6.1.4.1.25060.1.7 Successful Emails No Emails 1.3.6.1.4.1.25060.1.8 Unsuccessful Emails No Emails 1.3.6.1.4.1.25060.1.9 Email Alert Flag Yes Value 0..1 1.3.6.1.4.1.25060.1.10 SIP Received Packets No Packets 1.3.6.1.4.1.25060.1.11 SIP Sent Packets No Packets 1.3.6.1.4.1.25060.1.12 Allocated Memory Yes Bytes 1.3.6.1.4.1.25060.1.13 Calls Yes Calls 1.3.6.1.4.1.25060.1.14.x Trunk Calls Yes Calls 1.3.6.1.4.1.25060.1.15.x Trunk Status Yes SIP Response Code 1.3.6.1.4.1.25060.1.16 Uptime Yes Seconds 1.3.6.1.4.1.25060.1.17 Disconnects (no media) Yes Calls 1.3.6.1.4.1.25060.1.18 Disconnects (media timeout) Yes Calls The good old Wiki still has it: http://kiwi.pbxnsip.com/index.php/SNMP

Did you try to use the tone detection of the trunk? This is a generic tone detector built into the PBX (not the gateway). It is pretty generic, should also work in Australia.

Hmm.... Can you check what is in the outbound proxy of the phone?

There is a custom file that you can load after all other config files have been loaded. Check the generated/xxx/snom_xxx.xml file for the exact name (should be something like snom_320_custom.xml). Make sure that file exists and is in the html directory (relative to the working directory of the PBX). In this file you can put whatexer content you like.

If you are doing plug and play the PBX will already set it up this way. If you manually configure the phone, probably you have to go to the web interface and change the outbound proxy there (depends on the phone type).

We did a integration with CS1000 about one or two years ago. OMG. Multipart-MIME in the SDP. Anyway, we got it working. I would say give it a shot, and if it does not work try to get a SIP trace to see what changed...

Well, at least this is a sign that the phone is in trouble. Probably it tries the various DNS SRV entries that are available for the server when it fails from one transport layer to the other. What you can do is advertize only one transport layer or force the extension to use a specific transport layer (and thus rule out DNS SRV) with a outbound proxy like "sip:dns.name.com;transport=tls".

AFAIK you will also not gain any performance improvements as the code is pure 32-bit.

Oh that's a good one . Music on hold to someone who is parked... What happens if both sides park the call?

Indeed we added a feature that asks the phones to reboot when the buttons change. It is also available in the 3.4 release.

It is a feature that cell phones can get a call back. For people on the road it is very convenient if they don't have to try over and over to reach someone. If it does not work, that is a different story. If the PBX able to call the cell phone on other occasions, e.g. a new voicemail?

Sure. You can assign a different dial plan for the extensions located in the public areas.

Well, we have to do it right. Not sure if the other PBX want to end up in a security chaos where everyone in the network can turn LED on and off and program nice animation patterns for SIP phones in the office. Microsoft also takes security very serious. I am sure that there is a way to get this working in a safe way and we don't have to worry about this.

Well, maybe you accidentially used a server name that includes a "@" (as in account@server). Then the PBX would try to find the DNS entry for account@server, which obviously fails. Okay, would be stupid. But all problems are stupid! Apart from that, seems it is time for Wireshark and trying to find out what is going on.

How can the PBX know it is not a spoofed packet from somewhere in the network? Do you know if Exchange supports authentication (e.g. Digest)? We have no problem with unsolicited NOTIFY, but we want to make sure we don't generate a security leak.

We already have something in the address book (of course version 4), so that a caller that went through the agent group gets conected to the same agent next time he calls. Maybe that helps in this case.

What is the address of the server? Did you include a "@" in that? Seems there is a problem with DNS. Maybe just try to use a IP address and see if that changes the situation.

Though it is the voice VLAN that does not mean there is no HTTP traffic. In other words: You still need to provision phones and you still want the phones to pull down information (e.g. address book) from the PBX via HTTP. But I agree, routing between the VLAN is a new problem then.

Not yet. But it should be easy to add PnP if the software behaves like the other snom phones. We added MeetingPoint and that was very easy.

Very good now we can play music the whole day in the office...

There are not too many ceiling speakers available (AFAIK). We used a CyberData speaker in the previous office and it worked without any issues. There was also another post on this (http://forum.pbxnsip.com/index.php?showtopic=2868). I think there are also other systems like Mobotix which come from the video market.