Search results

In that case, my guess is that it may be a bug in the FusionPBX code that displays the list. Just to be sure you could check what is actually in the database, and if you see some records, check that the domain_uuids match the domain you are interested in. root@testpbx:~# su - postgres...

Did you add any? If you did, were they added in the same domain that you have selected now?

When you say "I already increase the max sessions in config.xml" did you mean /etc/freeswitch/autoload_configs/switch.conf.xml? Below is the relevant section of the FreeSWITCH switch.conf.xml as setup by default in DjangoPBX: <!-- Max number of sessions to allow at any given...

A couple of further ideas: I know you have tried un-setting the privacy headers, but the order may be important. Try <action application="set" data="sip_cid_type=none"/> <action application="unset" data="sip_h_Privacy"/> Another thing that may be worth trying is the mod_dptools...

You can edit the dialplan XML for the IVR and set a custom SIP header for the IVR UUID like this: Then you can set a custom header for any or all digits in the menu itself like this, note option2 is repeated with an incremented order number:

Be careful about just blindly switching to TCP. SIP was designed to use UDP for good reason, but does specify the need to switch to TCP if packet size becomes a problem. In this digital age we can so often overlook the simple and obvious. It could simply be a faulty handset cord or earpiece.

From what Mark says, I think it does, by only opening 443 if there is a valid registration from that address. but tying the two together does not work in all circumstances, hence my question to Mark. Freeswitch only deals with SIP, so events will not directly relate to anything going on on port...

@markjcrane Maybe one of us is missing the point, so please forgive me for re-phrasing my question. So what about an IP that has no valid registrations. For example all my phones are registered at my office, but I want to do some Admin from home, where I do not have any phones registered?

Hi Mark, I get EventGuard, we use a similar mechanism. But how does that work if you have a customer that wants access to admin facilities from an IP address that does not have any phones registered against it?

Generally speaking, if you have a working Fail2Ban or equivalent AND you have enforced good password strength, then you should be pretty safe. I believe in FusionPBX you can now also enable two factor authentication, which will provide another level of protection although many customers find it...

The key to successful diagnostics is "only change one thing at once", then re-test.

Looks good. There is no harm in changing the local SIP port, but what I meant was my PBX does not use 5060. It is the first measure in preventing the more simple router ALGs (SIP helper apps) from messing around with the SIP packets. On some of the Yealinks, you can set a different local SIP...

I don't use the common SIP ports, I vary them between installations but take 8060 as an example. Always UDP, no TLS or SRTP and the codecs in order of preference are G722, G729, PCMA.

I get that. I just can't see (at the moment) how or why FreeSWITCH is setting it. It does not get set in any of my tests. Just wondering if there is something else going on with the INVITE from the PSTN that is causing it to get set.

Thank you @johnny I will take a look at that. On the face of it, it does sound promising. Te Voicemail system on DjangoPBX is going through a pre-beta overhaul. It originally used Freeswitch mod_voicemail, but we have seen a good few feature requests that have required that we build our own.

I think by now I would be thinking either: 1. Change the door bell. 2. If you have an (and I hate the term) SBC anywhere in the link, such as an OpenSIPS proxy, then get that to rip out the header.

Welcome @mobi. You will find many helpful and knowledgeable people on here.

I would put money on it being the switch. We have had faulty switches that have sent packets to the wrong MAC address.

There have been quite a few major changes to the DjangoPBX codebase over the last few weeks. We are intensively testing the clustering arrangements and once we are happy them I will promote the software status from Alpha to Beta - after which there will be no breaking changes. I'm not...

Welcome, as @mcs3ss2 says, you will find some very helpful people here.