[Asterisk-Users] R2-Digital (Q.421)

[Jesus Mogollon]

That's exactly how they explained it works. The DTMF is only to provide DNIS
and using the register signalling. When I run testcall, I get the handshake
but when testcall sends the first digit, the remote equipment doesn't
recognize it (because it's expecting a DTMF signal) and then it times out. I
don't want to buy the Cisco for this :( especially when I wanted it to be a
full open source solution. What would it take for you to implement it?

2005/11/10, Julio Arruda <jarruda-asterisk at jarruda.com>:
>
> Just to clarify this in my head :-)..
>
> So...
> They are using E1/R2 (the R2 Digital)in fact, for all the line signaling
> (nothing unusual)
> The register signaling, that I was under impression would be MF in each
> timeslot (MFC5C in .br, not sure if the same in others), is in fact DTMF
> in this trunk, and only to provide DNIS ?
> (in Brazil R2, the register signaling has some collect call information
> and etc).
>
> Steve Underwood wrote:
> > Hi,
> >
> > I tried hunting for a little more info. I think all that happens with
> > this is they use the Q.421 spec for handling the ABCD bits, and then
> > simply send the DNIS through as DTMF after the seize if acknowledged.
> > That means they loose some of the functionality of real R2 signalling -
> > e.g. no busy, NU, or congestion detection. It wouldn't take a lot of
> > work to implement that.
> >
> > Regards,
> > Steve
> >
> >
> > Steve Underwood wrote:
> >
> >> Hi Jesus,
> >>
> >> The Cisco kit, and one or two other products, offer an R2 digital
> >> using DTMF mode, but this is the first time I have heard of it being
> >> used. The spec for this is definitely not Q.421. That spec does not
> >> mention DTMF at all. R2 using DTMF doesn't appear to be in the ITU
> >> specs, as far as I can tell. Without a spec, or any equipment to play
> >> with, there isn't a lot I can do right now.
> >>
> >> Steve
> >>
> >>
> >> Jesus Mogollon wrote:
> >>
> >>> Hi Steve:
> >>>
> >>> Thanks for your help. I really appreciate it..
> >>>
> >>> My provider is CANTV in Venezuela. There's a venezuelan variant in
> >>> the code and I'm using that. Incoming works perfectly, outgoing is
> >>> not working. I'm being told that incoming is MFCR2 but outgoing is
> >>> R2-Digital with DNIS DTMF. There is a Cisco router working and it's
> >>> using the following:
> >>>
> >>> r2-digital-dtmf-dnis R2 ITU Q421 DTMF tone signaling with DNIS
> >>>
> >>>
> >>> What's the equivalent in libmfcr2 and Unicall?
> >>>
> >>> Again, thank you for your help and your code!
> >>>
> >>> Jesus Mogollon
> >>>
> >>> 2005/11/5, Steve Underwood <steveu at coppice.org
> >>> <mailto:steveu at coppice.org>>:
> >>>
> >>> Hi Jesus,
> >>>
> >>> FX is not a variant of R2. It is a completely different signalling
> >>> protocol. This means your service provider is using R2 for some of
> >>> your
> >>> channels, and providing all your incoming calls on those channels.
> >>> It is
> >>> use FX signalling for other channels, and you must make your
> >>> outgoing
> >>> calls there. Someone else told be about a similar configuration. I
> >>> think
> >>> they were able to use chan_zap for the other channels, and make
> >>> use of
> >>> its FX signalling features. I am not sure how that works, as FX
> >>> signalling over E1s is far from standardised.
> >>>
> >>> Regards,
> >>> Steve
> >>>
> >>>
> >>> Jesus Mogollon wrote:
> >>>
> >>> > Steve:
> >>> >
> >>> > That's exactly what I'm using. Incoming calls work like a
> >>> charm but
> >>> > when I try calling I get a protocol error. My provider says
> >>> that for
> >>> > outgoing I need to use fx signalling. I see that in unicall.conf
> >>> > there's such a thing as protocolvariant=fx but if I uncomment that
> >>> > line, unicall gives me an error. Any ideas? Thanks for your
> >>> help...
> >>> >
> >>> > 2005/11/4, Steve Underwood <steveu at coppice.org
> >>> <mailto:steveu at coppice.org>
> >>> > <mailto: steveu at coppice.org <mailto:steveu at coppice.org>>>:
> >>> >
> >>> > Jesus Mogollon wrote:
> >>> >
> >>> > >Does anyone know how to make this work with Asterisk?
> >>> (R2-Digital
> >>> > >(Q.421)) I have MFCR2 configured but I'm told that outgoing
> >>> calls are
> >>> > >to use Q421 R2 Digital signalling. Any help is appreciated.
> >>> > >
> >>> > >Jesus Mogollon
> >>> > >
> >>> > >
> >>> > See http://www.soft-switch.org <http://www.soft-switch.org>
> >>> >
> >>> > Steve
> >>>
> >>
> >> _______________________________________________
> >> --Bandwidth and Colocation sponsored by Easynews.com<http://Easynews.com>--
> >>
> >> Asterisk-Users mailing list
> >> Asterisk-Users at lists.digium.com
> >> http://lists.digium.com/mailman/listinfo/asterisk-users
> >> To UNSUBSCRIBE or update options visit:
> >> http://lists.digium.com/mailman/listinfo/asterisk-users
> >>
> >
> > _______________________________________________
> > --Bandwidth and Colocation sponsored by Easynews.com<http://Easynews.com>--
> >
> > Asterisk-Users mailing list
> > Asterisk-Users at lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> > To UNSUBSCRIBE or update options visit:
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com <http://Easynews.com>--
>
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20051110/e7c5c571/attachment.htm