Thanks Sean, we do have a large number of systems deployed (several thousands of lines) so it's more cost effective than other solutions. We're developing the specifications through reverse engineering it, since there's almost no documentation, being an internal protocol from the early 80's not standarized. Nevertheless it's quite straight forward.
El mié., 27 mar. 2019 a las 14:16, Seán C. McCord (<ule...@gmail.com>) escribió: > > If you have the spec, and depending on your specific requirements, I can > probably get it done. However, it seems unlikely to be cost-effective unless > you have a large number of deployed systems to which this adaptation will be > applied. > > > On Wed, Mar 27, 2019 at 12:04 PM Alvaro Bosch <alvarobo...@gmail.com> wrote: >> >> Hi guys, >> I've been addressed the challenge to connect asterisk to a legacy NEC >> public system from the 80's that uses a custom protocol running over >> X.25/LAPB on timeslot 16 of an E1. The rest of the channels are like >> B-chans. >> >> I wonder if anyone can do it so I can hire the development services >> for such task. >> >> Kind regards. >> >> -- >> _____________________________________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-dev mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-dev > > > > -- > Seán C. McCord > ule...@gmail.com > CyCore Systems > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
