I just upgraded to Asterisk 1.8.4.1 (from 1.4.39.1), and even after editing and re-saving my inbound routes, they're still using pipes for the delimiters between the arguments, which is a deprecated syntax in Asterisk 1.8, and throws warnings in the logs.
[May 20 13:30:13] WARNING[23746]: pbx.c:1402 pbx_exec: The application delimiter is now the comma, not the pipe. Did you forget to convert your dialplan? (GotoIfTime(0:00-8:59|*|*|*?from-outside-19876543210-tl-off-hours|s|1))
(repeat the above line in the log for each line of the script - each route has several)
Yeah, I had PBXManager
Yeah, I had PBXManager 6.1.1.8 when I upgraded, and told it to update itself to 6.1.1.10 (which it did) after I upgraded Asterisk. I also went and edited one of the routes to see if it would write it back out with commas instead of pipes if I edited it, and it didn't.
Note that it all still works, it's just printing the warning in the log.
my 1.6.2.14 MTE box writes
my 1.6.2.14 MTE box writes these configs..
exten => +1502632????,7,GotoIfTime(*,*,*,*?from-outside-+1502632????-tl-allhours-dishonmkt,${EXTEN},1)
my 1.8.4 STE box at home writes these
exten => +1502315????,3,GotoIfTime(*,*,*,*?from-outside-+1502315????-tl-allhours,${EXTEN},1)
another example of the analog
another example of the analog line on my home pbx
exten => s,3,GotoIfTime(1:00-5:59,sun-sat,*,*?from-outside-s-do-not-disturb,${EXTEN},1)
Yeah, that's what I would
Yeah, that's what I would expect. Is there any way other than a reinstall to trick PBXManager into re-writing the configs?
inbound routes and pipes
Could you please check again if it did not generate correct code after you edited a route?
Yeah, turns out it's trying
Yeah, turns out it's trying to be smart and not changing the file if you didn't change anything in the route. So just loading the route and clicking Save doesn't work. I have to actually change something to get it to re-write it in the file (editing the description works). But that does only re-write just the route you edited. I ended up just opening inbound.include and doing a search-replace to fix the rest, way too many routes to do that manually in the web ui. :)
im not having that issue, are you running old thirdlane? After you installed 1.8 did you re-install your thirdlane so that it goes out and fixes its code and re-detects the version?