2011/11/2 giovanni.v <[email protected]> > On 02/11/2011 18.45, Olivier wroteo: > > 1. As the above line comes from libpri, how can one be certain the telco >> side didn't send the weird NUL byte ? >> > > Assuming libpri debug doesn't mess nothing is quite sure the NUL come in > from the telco.
So, would you still rate this as a libpri bug or a Telco issue ? I would say "if this is confirmed to come from the Telco network, then this is a Telco issue". > > > 2. Anyway, as Q.931 allows any IA5 (ISO 646) character, libpri should >> notify sysadmin for every non-IA5 character received >> > > But NUL is an IA5 character, so I think must be handled like any other one. > - http://skew.org/iso-ir-001/ Then, how should such a "valid but unuseful" character, if I may rate it as such, be handed, then ? To me: A. we should not expect any called number to include any character but those in the 0 to 9 range. B. we should notify sysadmin anytime an "unuseful" character is received (to let him, for instance, ask telco do whatever is needed for this to stop). > > > > -- > ______________________________**______________________________**_________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/**mailman/listinfo/asterisk-**users<http://lists.digium.com/mailman/listinfo/asterisk-users> >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
