Koozali.org: home of the SME Server
Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: compsos on February 10, 2014, 09:44:02 AM
-
In the past we could define a trunk with an * in the name but sail-4.0.0-103 it returns
field can only contain alphanumerics and no spacesOn the system concerned it has progressed up from 3.1 to 3.2 and now to 4.0 and 3 previous DIDs with the * made it into the extensions.conf mainmenu section. Otherwise we get this in the cli
Call from 'xxxx*00002' (xxx.xxx.xxx.xxx:5060) to extension 'xxxx*00001' rejected because extension not found in context 'mainmenu'.
How is it done in 4.0 to add a SIP trunk with * and associate to a DID? We can get a call in by modifying at the provider to change the caller ID to 6174203xxxx@ipaddress but then the users will not be able to use redial etc. This is when we use the DID as the name in the name field of the registration.
Thanks.
-
Might have answered my own question. Will test tomorrow.
Go to Routes-> Inbound and define the DID there. Now the mainmenu has the username code.
-
Hi Gordon
Yes - you have answered it.
In V2/V3 trunks and DiDs were quite blurred. You could define a trunk and assign a DiD to it in one entry. However, while this is OK for people who know how it works, it can be confusing, particularly for new users and those coming from FreePBX type systems where a fairly strict distinction is made between a trunk and a DiD. So we split them in V4. Trunks can no longer double as DiDs in V4 (well, they still can but only within the limits of a well-formed DDI i.e. a string of digits). However, in inbound routing, you can now assign any valid Asterisk dialplan to a DiD so it can quite happily be a number group (i.e. _6744XX.) and it can have any valid asterisk dialplan character included in it. It's more intuitive because it nicely falls into the routing section (along with the older "Routes" for outbound).
Best
S
-
...ps - 4.0.0-115 went up to the servers tonight - quite a few minor bugfixes over 103.
* Tue Feb 11 2014 Aelintra <coco@aelintra.com> -r2109 4.0.0-115
- fix regex bug in sarkddi js
* Thu Feb 06 2014 Aelintra <coco@aelintra.com> -r2108 4.0.0-114
- Suppress local IP display in globals if eth0 not present
- Change ASTDLIM to default to comma instead of pipe
- Fix error in js regex in trunks and ddi
- Add eth1 and virtual IPs to globals for Pacemaker
- Change AMACs syntax to generate fewer benign error messages
- Fix listenforext in IVR
- Allow route dialplans to begin with + or _+
- Modifications to callgroups to handle channel addresses
* Thu Jan 23 2014 Aelintra <coco@aelintra.com> -r2101 4.0.0-113
- Modifications to sarknet for Pacemaker
* Wed Jan 22 2014 Aelintra <coco@aelintra.com> -r2098 4.0.0-111
- changed header generation (header.htm)
- added hausecluster to provisioning for Pacemaker
- fixed provisioning bug for Snom760
* Tue Jan 21 2014 Aelintra <coco@aelintra.com> -r2093 4.0.0-110
- Mod support for sipsak monitoring from the localhost (used in Pacemaker CRM generation)
- Update f2b for shorewall in debian systems
- Update sipSQL for Pacemaker
- Add commit button to sarkedit
- Update Globals for Pacemaker
- Update responder for Pacemaker
- add selmixd for debian systems
- update shorewall.conf for debian systems
* Sun Jan 12 2014 Aelintra <coco@aelintra.com> -r2089 4.0.0-109
- Add support for sipsak monitoring from the localhost (Pacemaker)
* Mon Jan 09 2014 Aelintra <coco@aelintra.com> -r2088 4.0.0-108
- Debian ONLY release - this is just a placemarker
* Mon Dec 09 2013 Aelintra <coco@aelintra.com> -r2081 4.0.0-107
- Add support for Queuemetrics Ast1.8
* Mon Nov 25 2013 Aelintra <coco@aelintra.com> -r2075 4.0.0-106
- Fixed REGEX bug in route
* Mon Nov 25 2013 Aelintra <coco@aelintra.com> -r2072 4.0.0-(104-105)
- Fixed CLI hierarchy
- Fixed Custer allocation issues
- Fixed smartink bug
- Fixed leading zero on DDI
- Fixed dialplan / on route
- Fixed password save issue on User
- Added trunk active status to front panel
- Added extra validation to User panel
- Fixed benign Apache error log msg from sarkedit
- Changed release display mechanism in Globals
- Remove Asterisk and Provisioning tabs from User extension view
- Changed banner display mechanism
- Standardized alpha validation in js
-
Hi S
Just loaded 115, but it seems the header.htm file from the www was not included in the rpm. I have copied one from a backup, but you might like to check your build.
drwxr-xr-x 2 root root 0 Feb 12 07:44 /opt/sark/www
drwxr-xr-x 2 root root 0 Feb 12 07:44 /opt/sark/www/cgi-bin
-rwxr-xr-x 1 root root 434 Oct 9 2012 /opt/sark/www/cgi-bin/sarksnomrereg.pl
-rwxr-xr-x 1 root root 1100 Nov 18 2012 /opt/sark/www/index.html
-rw-r--r-- 1 root root 2679 Oct 14 07:03 /opt/sark/www/navigation.php
drwxr-xr-x 2 root root 0 Feb 12 07:44 /opt/sark/www/provisioning
-
Was this a new install or an upgrade?
-
upgrade from 103 to 115
So your thinking it should not have removed the existing file? the code in the previous post was from less on the 115 rpm file.
-
Just tried another system and same result header.htm was removed during the update.
-
header.htm doesn't get installed in place so you shouldn't see it in /opt/sark/www in the rpm (look in /opt/sark/cache).
it gets copied from /opt/sark/cache during %post if it doesn't already exist so I'm puzzled as to how it could get removed.
I'll run some installs/upgrades on the VM server but they should have already been done in testing.
how did you do the install (what rpm cmd did you run?)
S
-
Hi S
Ok we downloaded the file and ran either yum install sail...... or yum update ..... Both systems had the same result.
In a copy of the old sark directory the header.htm was in the www directory. And copying it back solved the frame having a 404 error.
-
Hi Gordon
The error is in the rpm %post We've pulled 115 and fixed it in 116. You will need to reboot after you put 116 on but it should be fine in future releases.
Thanks for your help with this
S
-
No thank you for the system. Only too happy to help where we can.