Search results

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.

Your PBX should not be responding with a 407 Proxy Authentication Required, on an inbound from Signalwire. Check that you have the Signalwire IP addresses in your "Providers" ACL. If you edit the ACL remember to reload it.

Hi @pbxgeek, Any collaboration is a good thing. I feel that we should combine ides rather than systems. I think the VoIP community as a whole will benefit from having more systems to choose from, especially if they are open and well supported. No two projects are exactly the same, each one...

@pbxgeek I watched your video, I like what you have done technically and it also looks very smart. The use of Laravel to handle tasks like database migrations is a real step towards better maintainability, it appears to work in a very similar way that the Django framework works for us. I assume...

I have just tried, various combinations of calls on two of our PBXs and I never see that Privacy header. I agree that Freeswitch must be generating it, but I wonder what the trigger is. As you say it only happens on inbound from an external number, I wonder if it could be a setting in the...

I think you may have to look at SIP_CID_TYPE or The DpTools application Privacy. https://developer.signalwire.com/freeswitch/Channel-Variables-Catalog/sip_cid_type_16352846/ https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Modules/mod-dptools/6587011/ Is the Privacy header...

My first thought is switch SIP provider to one that will do what you need. Depending on the type of communication you are thinking of using to pass this information to the other party, you could just send an arbitrary UDP message to the other parties IP address / port where you have something...

This thread references the same issue: https://www.pbxforums.com/threads/yealink-dect-crosstalk.7704/#post-31385 We have a lot of Yealink DECT including the W70B, but have not had any reports of cross talk.

You may find this thread helpful: https://www.pbxforums.com/threads/ivr-prompt-choice-not-dialing-in.5922/#post-23907

@pbxgeek I'm sure we will collaborate and share. I will drop you a line with my email address. Kind regards, Adrian.

I'm so glad to see someone else using a tried and trusted framework for a FreeSWITCH GUI wrap. It makes so much sense, removing all the worry of looking after the web interface and allowing developer to concentrate on what they are good at - developing PBX solutions. I have basically done the...

OK, if you are entering the correct provision username and password, then we may need to gig a little deeper. The 401 is an unauthorised error for sure. You can set the provision username and password either globally in default settings or an the per domain basis in domain settings. Make sure...

Sorry, I'll re-phrase. What ever username and password to put into the http_auth_username and http_auth_password variables. All you need to do is type the same into the sign in dialog when it is presented to you. You will then be authorised to see the config files that your phone would download.

The provisioning is asking you to provide WWW-Basic-Auth, which is the method used by the phones. It is different from the auth. mechanism used in the Web GUI. All you need to do is type in the http_auth_username and http_auth_password that you have used in the default or domain settings.

Very basically, if an endpoint registers using UDP, FreeSWITCH will report the registered status as UDP. If, however, FreeSWITCH, or more specifically mod_sofia detects any RFC1918 addresses in specific headers, Contact: for example, it will report the registered status as UDP-NAT. FreeSWITCH...

If I remember correctly the mobile-twinning app was written by @KonradSC. If you search on here for mobile-twinning you will find a few posts about setting it up, mostly from around 2021. I'm not sure if it is maintained, but we certainly got it working when we had a play with it on Fusion 4.5...

So if I read your sngrep correctly, your PBX makes no attempt to send an INVITE to your provider for the external number in the ring group, yet your application logs show a bridge to a mobile number via your gateway. I'm wondering if your sngrep is missing some information, especially as I...

What am I looking at? Are these successful calls? They don't look like it. Is this between your PBX and provider?

OK, it may need the name or IP of the Proxy in your case. The best way to check is to run sngrep and make a call out on that gateway that you know works ok. Then you will see what is being used as the invite domain for a successful call.