I don’t know if the GUI allows you to change the behaviour, but using anything but UTC is a bad idea unless you live somewhere that doesn’t use daylight saving time and you only use one timezone.
Using local time is the default for Asterisk, so it is certainly possible to set that at the conf file level.
Very interesting.
Running this:
[macro-dialout-trunk-predial-hook]
exten => s,1,NoOp(accountcode is ${CHANNEL(accountcode)})
Shows this when called via Sangoma Talk (mobile app):
841 [2024-05-28 11:02:15] VERBOSE[13277][C-00000002] pbx.c: Executing [s@macro-dialout-trunk-predial-hook:1] NoOp("PJSIP/200-00000002", "accountcode is TEST") in new stack
But shows this when called via Sangoma Desktop:
1014 [2024-05-28 11:03:07] VERBOSE[13556][C-00000003] pbx.c: Executing [s@macro-dialout-trunk-predial-hook:1] NoOp("PJSIP/98200-00000004", "accountcode is ") in new stack
So it appears that the issues has to be redefined as: when calling from Sangoma Desktop, accountcode does not seem to populate as variable in dialplan. Any idea why?
For my user case having a desktop app is a must have, so I really need to make this work.
It looks like PJSIP/98200 is callign rather than PJSIP/200, so it would make sense that being 98200 not having an assigned acocuntcode, it would be empty. But what is 98200 coming from?
I believe it is created automatically internally to allow the desktop client to work (WebRTC and non-WebRTC are incompatible from a configuration perspective) and presumably supposed to generally mirror the non-desktop client version. If accountcode isn’t mirrored, I would consider that a bug myself.
Nobody ?
That’s what I’ve done :
Unpacked .tgz backup file
Edited mysql-3.sql file, removing a bunch of extensions related rows
Re-packed .tgz file
Run restore
Ended with the same machine as before , less the unwanted extensions.
Now, I haven’t the knowledge to know if this ok , or just a lucky attempt that can breaks something…
I am sure @lgaetz will correct me if I am wrong here but pretty sure extensions starting with 98 are legacy Zulu extensions.
Not sure about the accountcode part of the whole deal.
After updating the freepbx modules something broke… it is no longer possible to search for contacts from Sangoma phone Desktop.
I don’t understand, and we have already asked support for explanations in the past, how it is possible not to know what is actually being updated! that is, if before when there was an update for example of the sangoma_api module the list of changes was reported, now with github we no longer know anything…it updates on trust, hoping that everything goes well, and it is not Always like that.
The bug of the day is that the groups created in the Contact Manager module are visible in UCP, in Sangoma Mobile but not in Sangoma Desktop and a search does not give any results, naturally the permissions to see these groups are there, but it doesn’t work
Following up on my own post… I’ve stood up a standalone machine and this is where it dies:
(from the install log):
The following NEW packages will be installed:
freepbx17
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 188 MB of archives.
After this operation, 598 MB of additional disk space will be used.
Get:1 http://deb.freepbx.org/freepbx17-prod bookworm/main amd64 freepbx17 amd64 17.1-1.sng12 [188 MB]
Fetched 188 MB in 13s (14.0 MB/s)
Selecting previously unselected package freepbx17.
(Reading database … 107054 files and directories currently installed.)
Preparing to unpack …/freepbx17_17.1-1.sng12_amd64.deb …
Unpacking freepbx17 (17.1-1.sng12) …
dpkg-deb: error: subprocess was killed by signal (Killed)
dpkg: error processing archive /var/cache/apt/archives/freepbx17_17.1-1.sng12_amd64.deb (–unpack):
cannot copy extracted data for ‘./home/asterisk/.npm/_cacache/content-v2/sha512/dd/59/915c4b70ed164a01ffb84efd589bd0067a8f2bf3e0a30e2dbac7eed26108a5d54aada9d6a8921ce8109a21aa5cedd26e6469c2520e1250906fcb5a1a5107’ to ‘/home/asterisk/.npm/_cacache/content-v2/sha512/dd/59/915c4b70ed164a01ffb84efd589bd0067a8f2bf3e0a30e2dbac7eed26108a5d54aada9d6a8921ce8109a21aa5cedd26e6469c2520e1250906fcb5a1a5107.dpkg-new’: unexpected end of file or stream
Errors were encountered while processing:
/var/cache/apt/archives/freepbx17_17.1-1.sng12_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
2024-05-28 15:10:49 - Exiting script
So it looks like the .deb file freepbx17_17.1-1.sng12_amd64.deb is corrupted?
Any suggestions on how to resolve this? Or fall back to a previous version?
PS: I’m a total noobie on FreePBX so if you talk to me like I’m an idiot you won’t be too far off. 
Also call log in desktop phone not works: “There are no calls”
@shahin - Did that. Virgin server build, but changed the resolver to 1.1.1.1 and 8.8.4.4 and no difference.
See my other reply; it looks like the .deb file for v17 is corrupt.
I appreciate you taking time to respond to me as I learn!
I was never able to get it working. There is now a note on the Wiki that the feature is in beta, maybe it will work by the time they decided to start charging extra for it.
I believe that nothing is broken.
A simpler approach is to do a bulk export, delete the unwanted rows in Excel and bulk import the edited .csv .
Hi @VoipMC Are you using 15 or 16? Could you please share the SangomaRTAPI, Manager, Restapps and SangomaConnect module version details? Thanks
tried just now in freshly built debian VM on Vultr and it worked fine.
freepbx17 package is quite big in size so may be some issue from your end to download the package.
How much memory does the system have? What does “dmesg” show for output (such as dpkg-deb getting killed due to being out of memory)
I have a PJSIP trunk that is working well, the problem is all the DID numbers for the inbound calls have “>” sign at the end of the DID number, in order to solve this issue I have used a format of " _+251xxxxxxxx1." in order to match the exact DID number; this solution also works but the problem again with this format is when I send the destination of incoming call to other trunk it is sending the DID as “+251xxxxxxxx1%3e” (%3e is the hex char value of >).
What I want is to change the extensions_custom file and to manipulate the DID like this
If there is other solution do not hesitate to inform me.
Thanks.
It won’t connect to FreePBX. I get an error on the admin page as shown in the first pic, see SIP Status. 408.
yes, ok
The 408 indicates that the device received no response to its registration requests.
Probing that address from here, there is a valid response from “JvDServicesPBX”.
Possibilities:
If this PBX is local to your site, your router/firewall may not handle ‘hairpinning’ correctly; use the private LAN address of the PBX instead of the 162 public IP.
A previous request with e.g., wrong password, may have caused your IP address to be banned by fail2ban – check under Intrusion Detection tab for FreePBX Firewall.
If you still have trouble, check whether registration attempts appear in sngrep. If yes, check FreePBX firewall settings. If no, check network settings, capture traffic leaving phone, etc.
Thanks for the information. I was hoping there’s some GUI option I had missed.
I don’t want to start messing with conf files.
