[retronet-octoi] Fixes in DIVF dialplan / your help required

Greeting from the engine room! During RetroNetCall earlier this week, we had a live debug session for the dialplan on DIVF, the yate based softswithc we use as central switch within the OCTOI network. We were able to collaboratively fix a number of bugs (mostly reported by cquirin), which means we are catching more cases in which we were doing something wrong in the past. For those not that familiar with ISDN: In ISDN you not only have a string of dialled digits (like in analog POTS), but you also have the numbering plan indication and type-of-number fields together with a number. So both calling and called party can be in many different formats, and we need to try to make sense of them in the various situations, convert them to the most suitable format at the given point durin processing, etc. The fixes implemented might cause some existing setups to suddently fail. This is due to the fact that DIVF was doing something wrong in the past and has been fixed now. If you previously configured the equipment on your end to expect/generate the wrong format, you might need to make the corresponding change at your end. So please do a round of re-testing and reach out in case anything is not working for you, or you need clarification. I apologize for any turbulence this has caused, but I do think we all agree we need to aim to configure everything as proper as we can, to resemble the public ISDN service of the past. Thanks for your attention, Harald -- - Harald Welte <laforge(a)gnumonks.org> https://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)