InterLinked1

> Unless it was done in an optional manner that defaults to maintaining existing behavior. I'd rather not add unneeded complexity to work around a bug just to get it...

> Could you please explain "administrator's business logic."? > > As I understand with this module the SIP phones can synchronize with the Application Server the status of the features:...

> Also big question about multi subscriptions/registrations. For example if the SIP endpoint has 2 registrations and both of which support the feature synchronization then the Asterisk should send NOTIFY...

> > > Could you please explain "administrator's business logic."? > > > As I understand with this module the SIP phones can synchronize with the Application Server the status...

> There is Sorcery In-Memory storage module. https://wiki.asterisk.org/wiki/display/AST/Sorcery Good to know, but not really relevant here. That's just a backend that stores settings in memory, it's not how *I* store...

> ``` > cherry-pick-to: 19 > cherry-pick-to: 20 > cherry-pick-to: master > ``` PRs should be raised against master, not 18 (unlike Gerrit, it makes a difference now). And it...

> master is slightly different. It will not cleanly cherry-pick to branches from master. Is the process still go to to master first? Make separate PRs for each branch? Ah,...

> There is precedent elsewhere for the Caret separator when things get clever eg. Dial() 'b' and 'B' options. The ^ and other characters are generally only used for suboptions...

cherry-pick-to: 18 cherry-pick-to: 20 cherry-pick-to: 21

@asteriskteam Would someone mind giving this review in particular a look soon, if they have time? Don't want to nag, but because of the monolithic architecture of chan_dahdi, it's very...