Vodia PBX

Do you find the trunk in the trunks/xxx.xml files? If the answer is yes, something went wrong with the deletion.

At the moment it is pretty much hardcoded to 240 samples per day (that is every 6 minutes). Regarding the maximum, you don't miss anything - it precisely calculates the maximum within that 6 minute window.

Okay, we added 13: Number calls (not call legs) and 14: Number of calls on a specific trunk. The trunk number must be the index of the trunk (to locate it see the XML file name in the trunks directory). For example, if the file name is 25.xml then the OID would be 1.3.6.1.4.1.25060.1.14.25. Check out http://pbxnsip.com/protect/pbxctrl-3.2.0.3138.exe for a build that has these two additional OID. Would be great if you can verify this.

Maybe it really checks the www.pbxnsip.com URL. There is no document and maybe that is a problem for ASP.NET.

I dunno understand. You need 3.2 software for that, is that what you mean?

I am not the big expert on SNMP... Is it possible to pass a string to the GET request? Then the SNMP tool could tell the PBX what trunk it is interested in. That would simplify the setup. Otherwise we would have to assign a OID to every trunk. That would not simplify the setup.

Okay, that helps. Obviously, one way to use it is to set it up to the corporate Active Directory. You don't need the PBX for that.

A difficult topic. I believe if the user agent advertizes RFC2833 (the new number is actually RFC4733) the PBX has no motivation to burn CPU resources on analyzing it. Yes, you should see "DTMF: Power:" on log level 9 (Media).

Regarding the IP address there are esentially two possibilities. The first is to use DNS SRV entries; in this case it is the SIP device's job to locate the secondary server. The second is to give the new server the same IP address; this avoids the requirement for DNS SRV. However it has the problem that this setup can easily result in an IP address conflict - espcially when the primary server restarts and the old IP address is still active (which is very probable in the case of a sudden shutdown).

Yes, that is on the list. I am sure that once that we have the feature people will try it out, have a lot of problems, they will pick up calls and nobody connectd (because someone else picked the call up), their phone bill will explode (talking to a lot of mailboxes all the time and waiting for the "1" to connect the call), cell phone mailboxes will be full, their lines will be busy all the time (because one incoming call triggers multiple outgoing calls), the QoS to the ITSP will be hell (because practically nobody has a call limitation) and so on. But if customers are demanding it, we will put it in. Just want to keep the expecation level reasonable.

Hmm. A search for "LDAP" does not return a result...

They are fine. So you are saying other emails in the domain are working fine? What version and OS are you running? I remember there was a bug in this area, maybe you just need a newer version. In version 2, the PBX will present the tel:alias number. This number is supposed to be the number than outside parties dial. The internal number can be "embedded" in other places, for example the conference name (okay, that's a workaround).

We have good experience with AudioCodes, Mediatrix, Parlay, Patton, Vegastream as seperate gateways. Also there is the AVM FritzBox if you want BRI. If you want to use PC cards, there is Sangoma and Dialogic that offer SIP-based cards. We try to keep http://wiki.pbxnsip.com/index.php/Interoperability_Pages up to date.

The problem is simply that most (all?) phones have only one storage place for MWI and the last message is stored. The workaround is to register two extensions (all phones can register the same 2nd extension), then the phone will receive the MWI on two different accounts (one private and one shared).

Any chance to make a backup and move to 3.1.2? Anything in the logs? How did you enter the email address or the email addresses? Eh, I nix understand... You mean how the conference room is represented to the outside world? Nope. It needs to be a scheduled conference because this is the only way to pull the WAV down the web interface.

Oh I did not know they support LDAP... That would be another way of reason the address book! Any links to that?

Yea, I would say emails are more popular for immediate alerts than traps. In then end, the SNMP tools do nothing else than sending out emails. SNMP is great for monitoring resources 24x7, and there are a lot of great tools available. But for events, IMHO emails are easier.

Maybe a simple problem with the TLS negotiation. Anyway, you can use the global setting "smtp_starttls" to enable or disable TLS. Set it to "false" if you want to disable it.

There is probably a problem with the DTMF codec negotiation. Try the latest Grandstream firmware or try setting the codec on the phone to 101, that's the codec the PBX will propose.

At the moment you need to use the Windows Server features for failover. Those features include file system replication, and also service recovery. Don't ask me details, I just heared it is possible to set everything up. And it costs more than you pay for two PBX licenses together. Seems like the OS vendor knows how valuable this feature may be! For the next major release, we want to make this job easier and include some basic settings that also automatically bring up a secondary service. If you can wait a little, you can just make sure that you run a backup job every night and have a second server ready to go when the first hardware fails. Then the failover would have to be done manually (or by a hand-crafted script).

The double @ looks very suspicious to me...

In 3.2 we added a new graph that shows how many calls the PBX processed during the day. See below.

That is a difficult topic. First, the question is: Who wants to read the directory? If it is the phone, then we have a couple of methods. Polycom gets the address book provisioned after the reboot, snom pulls it down in its XML format (via HTTP), and there are new ideas about using XCAP for a more interoperable way of having an address book. If it is the PBX that should pull down the directory (especially from a ActiveDirectory), that is a completely different topic. And then we have a new topic coming up. LinkedIn, Xing, Salesforce, and I-don't-know what social networks are storing a lot of very interesting data (even with pictures!) that users would love to see on the display when a call comes in. A standard? No way. Everybody doing it in a different way. That is not making our life easier...

Well, I don't see a lot of traffic, but no NOTIFY... Either that is the problem or the logging wasn't turned on the that. It would be good to see also the SUBSCRIBE for the resource.

You need to log the SIP packets, SUBSCRIBE/NOTIFY. They are usually logged on level 7, unless you monitor a specifc IP address.