Search results

*98 works if I open the voicemail of the selected extension, does that mean that I've got a dialplan issue with *97?

OK, so there's two different, probably unrelated problems here.. On the first system, there are quite a few Say modules that aren't loading, with EN being one of them. Attempting to start it is giving: -ERR [module load file routine returned an error] More pressing issue has become that any...

I'm not quite sure what is happening here, but the symptoms are as follows. This was a previously happy system, with the exception of the issues detailed (and solved) here. - *98 works, but phrases are silent where Callie used to say 'pound'. Logs show Invalid SAY Interface [en] - *97 hangs up...

5.1.0 after updates today.

OK, working now. Not entirely sure what was the root cause, but it seems like something quirky in the database. Specifying the codecs in the sip profile allowed calls to connect, but were going immediately to 'busy', not to the ring group. Checked the ring group, the destinations weren't working...

Yes codec negotiation is set to generous. I can't understand why my setup is only offering G722. Will keep digging...

Yes that's how I was reading it too. I can't understand why it's only offering that though, the SIP profile is using the global_codec_prefs variable, and that variable is set as PCMA,PCMU,G729,G722

Hi all, just had this occurring on one tenant. Inbound calls are not connecting - just coming up as call ended. Nothing in call detail records but getting the following in the logs: 04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [NOTICE] switch_channel.c:1123 New Channel...

I haven't tried, but in my case I don't think things are even hitting the queue, the missing email_from parameter might be breaking the chain before it even gets that far. I might try an update tonight and see if anything has been changed.

I haven't had a chance to get back to it sorry, will have to have another look probably early next week at this stage

No, my symptoms are identical to yours; the test email works fine, but doesn't appear in the logs; there is nothing hitting the queue or the logs when a voicemail is saved.

I'm getting the same error on a new install, version 5.0.5 b620b36f28f828dd9a9951b73983af667a5adb51, Deb 11. 2022-11-09 11:32:59.139487 95.37% [ERR] switch_cpp.cpp:1465 [database] can not bind parameter: undefined parameter: email_from 2022-11-09 11:32:59.139487 95.37% [INFO] switch_cpp.cpp:1465...

Possibly the same issue as here, as yet unresolved. What are your logs says when you receive the call? Maybe unrelated, but are your extension numbers all numbers or alphanumeric?

Another data point... I've been having simliar trouble on a clean install. My hypothesis is that it has to do with my use of alpha characters as part of the extension code. Rightly or wrongly, I do this because looking at the logs it seems that anyone who tries to brute force the system only...

On the off chance, I recreated the extension and the device from scratch but used a different extension number, and the phone provisioned correctly and registered immediately, If I was guessing there might be an issue with copying that creates a partial record in the database... I don't have the...

Hi all, I've just spun up a new instance of FusionPBX on a shared hosting platform that I've used a few times. Everything is going normally, until I get to trying to provision a Yealink W70B/W56H combo unit. There are 2 x T53W units that are on the same network and provisioning, so I'm...

Thanks @markjcrane! All fixed an seemingly happy on my side now.

Thanks @markjcrane, I've just retried the install on my side (Deb 11) the initial errors are fixed as you noted, if it is helpful my system is now producing the errors below, and I'm unable to log in using the printed username and password. Processing triggers for man-db (2.9.4-2) ... CREATE...