Search results

Sounds like it could be tricky to diagnose. I would start with a packet capture on your Fusion instance to see exactly what the push server is doing, it may be de-registering because it has lost all contact with the phone. Do Zoiper offer any push service logging?

The push notification service is the only reliable way, the OS puts apps to sleep to save battery life so keep-alives don't work well and neither do low registration times. With a push service, it will be the push server that you see registered when the app is idle, not the app itself.

Here is a screenshot from my default settings page, PCMA is enabled and PCMU is not: PS: Customers sounding like Darleks may be an indicator of network issues which are not forced to only effect G711 codecs. It helps to fully understand exactly what the problem is before going for a solution.

I know the problem!!

Welcome.

I don't the answer, but I rather suspect that it is not possible. Try starting a new thread with that question and see if you get any useful responses.

Yes, by default is is set to rfc2833 in the SIP profile. You can override it using channel variables as shown in the link above.

OK, look at how the DTMF is being transmitted. On your FreePBX logs it looks like the keypad digits are being transmitted using SIP INFO messages as opposed to rfc2833. You may have a mismatch of DTMF types when using FusionPBX. https://freeswitch.org/confluence/display/FREESWITCH/dtmf_type

But even in your freepbx log we still see the 405: <------------> [2021-10-14 17:22:51] VERBOSE[32145][C-00000005] chan_sip.c: Sending text <locknumXML> <lockNum>0</lockNum> </locknumXML> on SIP/2000-00000008 [2021-10-14 17:22:51] VERBOSE[32145][C-00000005] chan_sip.c: Reliably Transmitting...

I have used GSM in the past, not quite as tight as G.729. Opus is a good modern contender, it is gaining wider support and something I'm considering moving in to live, just a few more weeks of testing to go yet. We all know that codec transcoding consumes valuable CPU time and we like to...

Customers in rural areas of the UK with really poor internet connections.

I would expect the key press to go as an RTP telephone event, I'm trying to understand how this SIP message fits into this jigsaw. There is more going on than just the dialogue between 192.168.0.70 and 0.80 because 192.168.0.71 is also mentioned. Does the DTMF payload between two devices cause...

The SIP message method type "MESSAGE" is part of a group of SIP message methods called Extension Methods. MESSAGE is used to send Instant Messages, the message being contained in the body as a MIME attachment as it is in your case: Content Type: text/plain ... <LocknumXML> <lockNum>0</lockNum>...

I Assume that the Yate device is telling you that whilst it understands that you are wanting use the MESSAGE method, this message type (MESSAGE) is not allowed for the address specified in the request URI.

The directories under /var/www/fusionpbx/app/scripts/resources are largely all just for staging the install or upgrade. The file I believe you need to edit (depending on your actual set up) is: /usr/share/freeswitch/scripts/app/xml_handler/resources/scripts/configuration/callcenter.conf.lua

The voicemail "beep" is defined in /usr/share/freeswitch/scripts/app/voicemail/resources/functions/macro.lua --beep if (name == "record_beep") then table.insert(actions, {app="tone_stream",data="L=1;%(1000, 0, 640)"}); end I have...

You will find things easier with 9 or 10.

I don't think the install scripts yet support debian 11 (bullseye). The error is probably because the install could not work out what version of PHP/FPM to install. Buster, Stretch and Jessie are currently supported. If you need debian 11 right now, you will need to modify the install scripts...

@fusionpbxnoaudio I do agree with you, an obscure port does reduce the amount of attempted connections, in fact just switching to TCP can make a difference. However I have never been a fan of "security by obfuscation" - some malicious entity will find you eventually! I employ a tactic similar...

The Federation of Communications Services (UK based) put a bulletin out about this a few weeks ago. If you are a member they have offered to look at logs etc with a view to getting the attackers closed down. DDOS can be tricky to deal with especially if you are on the end of a limited...