Search results

As Dave Gray has noticed there are problems with FreePBX updating pjsip-endpoint.conf. I've found that if extensions are imported from csv file you need to go to each extension in turn and re-submit. This seems to create the missing entries and allow the extensions to register.

Upgrade script run OK but version stays at 13.6.0 Checked CLI to confirm new build time. Initial testing seems to show that the problem has been fixed. Leads me to think that something went awry during the initial compile. Thanks

I've just moved a couple of phones using PJSip across to the old system and can dial between them OK. Both are ESXi VMs running Ubuntu 14.04.3 LTS. The new (problem) one Kernel Version 3.19.0-30-generic (SMP) x86_64 and the old one Kernel Version 3.13.0-65-generic (SMP) x86_64. As previously...

An update on this one. I have a mix of pjsip and chan_sip extensions (I need distinctive ringing on some phones and pjsip won't pass ALERT INFO in FreePBX12 although it is supposed to be coming in v13). Any call which terminates in a chan_sip extension works fine regardless of source type and...

May not be relevant but both phones are on local network and have ICE support set to no in GUI

I have same problem Asterisk 13.6.0 Incredible GUI 12.0.30 running on Ubuntu 14.04.03 in VM on ESXi. I messed up my previous setup and whilst I got it back up it wasn't quite right so created new pbx and copied extensions etc over using csv export / import. I have the same errors and likewise...

Installed on ESXi VM and unable to shutdown / restart gracefully. I've run update from CLI but still no joy. Any suggestions?

No problems apart from keyboard (presumably not PIAF problem) - installed on Intel Atom based machine, swapped sda sdb as per instructions - all OK. Had already formatted USB stick as FAT so don't know about using windows format.

Thanks for that. I'll try the new version once it's available.

As is script not extracting Freepbx version due to sed referencing wrong line in modules.xml (see attached file). I've done a simple fix but a more robust solution would be to search for the version tag. I'm not that familiar with 'sed' but will have a look when I get a chance unless someone...