Vodia PBX

If the code for turning the recording off simple? For example, if the code is "*" then it could happen that the recording gets turned off accidentially. I assume that we don't have a problem with file system full here.

Some routers also call their gateway "UPnP" (because the old Microsoft Messenger uses UPnP for getting a public SIP identity). Maybe you find something on the configuration page with the name "UPnP" and turn it off. You do TLS on the SIP phone (and also on the PBX, but there it is available by default). It is like using the web browser with https - here the router also cannot see the traffic. If you get a FritzBox 7270 then you can also use the ISDN gateway built-in to the FritzBox (see http://forum.pbxnsip.com/index.php?showtopic=1855).

Yea currently this is a bit difficult to use. In the next major release we try to put more loud speaker symbols (like in the mailbox) in the web interface so people can just click to listen to the prompts.

Well, you can specify a pattern like xxxxxxxxxx in the dial plan pattern that should do this job. What you can do is use a pattern like x|xx|xxx (after the x11 patterns to deal with 911!) and use the "not allowed" pattern, so that teh PBX does not attempt to go out on a trunk. Alternatively, if you only use xxxxxxxxxx and 011* patterns then the PBX never attempts to send anything but NANPA numbers and international numbers to the trunk. You mean ring tones or ringback tones? The ring tones should already be there, but of course that depends in the SIP world on the endpoint.

Try to explain the customer that he has to use the star codes to use these features. IMHO still reasonable, in the glorious old PBX days it was the same.

So mean there was a problem with a software upgrade? What version are you using now?

There is a setting called "Maximum Duration of Call Recording". Check if it is set to something reasonable.

Maybe the problem is not so much the cell phone, it is the redirection. The PBX probably presents the original caller-ID and the trunk provider rejects it.

I believe that will be difficult to the level that it is not possible. IMHO it is the job of the web client to store the username/password. If the PBX would already include the credentials in the email the security would go down to close to zero, as such emails tend to be forwarded and copied.

Try grep -H "Domain: 12" * if the domain number is 12. You can see the domain number when you move the mouse over the link to go into a domain.

Well, glad it works now... Could it be that the phone sends INFO and DTMF at the same time? I remember that was a problem sometime ago.

Nice. Do they have an application layer gateway? If yes, try turning it off. ALG on a router are in most cases more trouble than they help anyway. Or use TLS, so that the router just forwards encrypted traffic that could be HTTPS.

That part has not been touched yet, but 4.0 is not finished yet

Maybe the way the key press is sent to the PBX is a problem. I remember Grandstream was a big advocate of INFO. That might be a problem as info is not a "tone".

The other way of doing this would be disabling call waiting on the phone. Of course, that is a phone specific thing and you need to change it on the phone.

Well, the key point here is that the phone must authenticate themselves. The PBX no longer trusts the MAC address mentioned in the provisioning request. That has some very obvious security features; however it also requires that the endpoints now must have the username and password for provisioning before the provisioning can take place. There is a workaround for this. You can generate the MAC-based files and put them into the tftp directory. For details, ask support@pbxnsip.com.

Hmm. Does DTMF work with the phones? If you call the mailbox, can you navigate?

You can limit the number of "lines" for the extension to "1". Then that user will have only one call, no call waiting locally on the phone. That will make the PBX roll over to the camp on/mailbox immediately when that user is talking.

The files in the spool directory are ASCII readable. You can use grep to find out which domains are affected. But if the files have been deleted, that means they probably made it out. The PBX tries 50 times to send it before it deletes an email. Every trial takes a long time, maybe 5 minutes timeout.

Check out the content of the "spool" directory.

I was talking about the "Permissions to monitor this account"... I believe that is the right area because it deals with the question who is allowed to monitor someone.

Yea. That is not the first time we hear that. I am wondering if there is something that we can do in the permissions field which is backward compatible and solves that problem. For example right now, "*" means everybody can see everything. Maybe we use something like "*|a" to indicate that the caller-ID should be hidden.

You mean the "dialog state" (Permissions to monitor this account)? Are they using the button mode or the IETF dialog RFC?

Same here

That looks like a pretty straightforward setup... What about the SW upgrade?