Vodia PBX

Well you could run it on a small appliance (e.g. https://gitstorage.com) and also it should be possible to run VLC on the very host that runs the PBX.

The WAV files are now available, we are in contact with Vonex am I believe they will drop them into the audio directory shortly (this does not require a restart). This should make it lot easier to use the service flags.

We had another post about keeping deleted files for some time. Looks like the problem with the FAX is related - we need to add an expiry date for messages. Then it should be possible to automatically have messages drop out gently.

If you put the ACD on a button button you don't need to change the pickup preference (this should actually contain only orbits if remember correctly). Generally there is the "promise" that if a LED is blinking that the user can pick that call up. I think for the ACD we have more of a permission problem - should someone outside of the group be allowed to pick up the call? I remember we had made a change in the area so maybe the next version might already solve the problem.

The thing is that the call can hit numerous places like ACD, hunt group, extension and other stuff. Each group has some kind of logic what to do with anonymous calls, e.g. send the call though a call screening first when calling extension (which is pretty powerful). We did not want to drop those achievements and thus treated the SPAM scoring as a way to classify a call as "anonymous" and then go from there. If there is anything that we need to change along this way e.g. have an option to send anonymous calls to voicemail well then we can add it in the right place. But IMHO we should have that already?!

How about VLC?

At the end of the day we need to add an attribute to mailbox messages that says when it expires. Even new messages would expire eventually (e.g. default one year). Recovery would have to happen through the web interface.

There was a bug where it would initially permanently whitelist addresses for the trunk, then when there was a call, it would whitelist if for the duration of the call, well and when the call ended it would delete the entry. Then the trunk was essentially not whitelisted and this could lead to blacklisting. Anyway, as we make build for 61.1 that problem should be fixed in the latest build.

In the "Routing/Redirection" section of the trunk settings, there are several ways to get this done. There you can set the source to "To-header" (not the request URI). For pulling out your extension in Europe is usually easy because all numbers have a certain prefix that you can put into the "match extension after prefix" mode - for example if 954 would be your extension you could set the prefix to 752422. This way you don't have to set up DID for each and every account and just use a general rule how to find it from the caller-ID.

So you want to use call forward? Then you could set up a trunk from A to B (gateway mode) and make a dial plan entry that makes sure that redirected calls are sent over this trunk. For example you could redirect calls to "7771234" and then use 777* as the dial plan entry and * as the replacement, so that B will see only the 1234 in the SIP INVITE., If someone else understands please chime in...

Maybe I still understand what this is about... Do you want a redundant system, so that when one system goes down there is still another one taking over? Most SIP trunks can have one than one registration, so if you have a SIP trunk on A then you can use that same trunk also on B - so that both a and B are registered to the SIP trunk.

Well what you could do is to just register the SIP trunk on both systems. Then you will get that behavior.

There are several to get this done. One key question is how this redirection should be triggered?

There is a log category for ACME (which is the protocol that letsenrypt uses). Try putting it to 9 so that you see everything that is going on. If you put your dnsmadeeasy key in, it will not use HTTP and only try the DNS challenge - again this should be visible in the log. The whole thing gets triggered when you set up a new domain or when you set the management address for the PBX. The PBX checks every 24 hours if a domain certificate will expire and then will trigger the issuing of another LE certificate. Grandstream has changed their RPS API, it seems that this change was not backward compatible. If you want to give that a try, you will probably have to move to 61.1.

You might have to tell the Patton that is should not generate its own ringback and instead use the one coming from the PBX...

If you want to use letsencrypt your server must be on a public IP where the DNS name points to your server. Port 80 must be used. If run your server on a private IP address, you can still use letsencrypt, but must use a DNS hosting service. The only one we are supporting right now is dnsmadeeasy.com.

The new ANI is much more flexible than the old, hard-coded way: https://doc.vodia.com/trunk_ani

I would generate a PCAP for the call and listen to it. Maybe your trunk provider just does not accept it anyway? If you call the hunt group from an internal extension, do you hear the ringback then?

That should be fixed. A glich with the new Vodia website...

You can put the extension number into the hunt group and then enable the forking on extension level per extension and for the hunt group on that hunt group. There is no need to put a star code into the hunt group stages, it actually would not work. You can also just put the cell phone number directly into the stage.

This should be working again in the next version.

This sounds like a problem with SRTP and the crypto attribute in the Re-INVITE.

No - the configuration is mostly the same. You will have to re-check the trunk settings especially the headers and the button assignment for the phones has to be redone. But the rest should upgrade seamlessly.

Please make sure that you have the build from Sep. 9 this one should include it (works for me)

Actually for US-en you might just re-install the US-English prompts again, they should contain the missing files.