Yes,Mine did not work without creating an inbound rule even though the 390_mobile_twinning.xml file was copied to that path.
boom, this got it working for me, changed the order and did app defaults, cheers Adrian!Yes,
I have realised that the upgrade instructions do not include Add Defaults - there may be a good reason, but I have put in a pull request with an update. App Defaults (amongst other things) reads the xml files in /var/www/fusionpbx/app/dialplans/resources/switch/conf/dialplan and makes sure they get picked up into the dialplan.
I also noticed that 390_mobile_twinning.xml did not have the order="390" attribute in the extension tag.
Once I had run App Defaults, with the modified xml file to include the order, mobile-twinning appears in the Dialplan Manager:
View attachment 2097
//check for a valid 10 digit mobile number
if (strlen($mobile_twinning_number) != 10) {
if (strlen($mobile_twinning_number) != 0) {
$msg .= $text['message-warning'].$text['message-invalid_mobile_twinning_number']."<br>\n";
}
}
Thanks a lot AdrianIt is a while since I looked at the code for this, so I can't remember all the details but a good start would be to edit:
/var/www/fusionpbx/app/mobile-twinning/mobile_twinning_edit.php
and change the if statement shown in the code segment below:
Code://check for a valid 10 digit mobile number if (strlen($mobile_twinning_number) != 10) { if (strlen($mobile_twinning_number) != 0) { $msg .= $text['message-warning'].$text['message-invalid_mobile_twinning_number']."<br>\n"; } }
No, not really, because you have told us very little about your system.Any ideas how to fix it?