Hello, Redirection reason is not PRI-specific. For example, all terminal channels (FXS, Skinny) and some trunking channels (like H.323) is possible to generate real reason of redirecton. Also, SS7 is redirection-reason capable too.
IMHO at least trunking interfaces (IAX, H.323, PRI, SS7, etc.) should be capable to bypass redirection reason and other telco-related information. WBR, Paul. ----- Original Message ----- From: "Kevin P. Fleming" <[EMAIL PROTECTED]> To: "Asterisk Developers Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, September 28, 2005 4:42 AM Subject: Re: [Asterisk-Dev] Redirection reason > Kristian Nielsen wrote: > > > It wasn't clear to me from you message: Would you accept a patch that > > added redirect reason to struct ast_callerid, or would you prefer to > > stick to the PRIREDIRECTREASON variable, with the limitation that > > entails? > > I think it makes sense to leave it the way that it is for now, since > it's very PRI specific. You can opt to copy it into an inherited > variable early in your dialplan so that it gets copied into all new > channels that are created, though. > > > [We have the need to pass redirect reason between two different channel > > drivers we are writing, and I thought adding to struct ast_callerid was > > the cleanest way.] > > It could be, but it would also increase the size of that structure for > all non-PRI uses as well, which might not be too helpful. > _______________________________________________ > Asterisk-Dev mailing list > [email protected] > http://lists.digium.com/mailman/listinfo/asterisk-dev > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev > _______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
