[asterisk-r2] Incoming Calls DROPED with only 1 DNIS digit.

Wed May 26 12:42:44 CDT 2010

Other possible cause for your problem is immediate=yes in chan_dahdi.conf

With Unicall works because unicall does not check the asterisk dialplan or
the immediate option, unicall always request all possible DNIS ignoring any
configurations ( other than max_dnis ).

Moises Silva
Senior Software Engineer
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3
Canada
t. 1 905 474 1990 x 128 | e. moy at sangoma.com

On Wed, May 26, 2010 at 1:18 PM, Arturo Ochoa <arturo.era at gmail.com> wrote:

> Thanks Moy,
>
> And just for the records, I couldn't find any wrong configuration, or
> something else. I spend all day trying to figure it out, but didn't
> get the solution. Problem is, this server was in production, and they
> were out of service for all day.
>
> An the end, what I did was rolled back the asterisk 1.2 branch with
> Unicall, and without any special configuration, it started working
> just fine. I felt frustrated for this situation.
>
> This in short, is what I did:
>
> Original server Centos 4 with asterisk 1.2 and Unicall plugged to 1
> Telco and Ericsson PBX.
>
> Replaced with Elastix distro, then trying with openr2 1.2.0 and
> asterisk 1.4 packaged with Elastix... and not working on incoming
> calls.
> Then, upgrade to openr2 1.3.0 and compiled everything else (asterisk
> 1.4.28 with openr2 patch)... at the end same behavior.
> I tried even with timeouts, using the r2proto.conf... but same result.
>
> At the end, I compiled every library required to get unicall working
> with asterisk 1.2, replace dahdi with zaptel.. And it suddenly started
> to work just fine, incoming and outgoing calls working right, this is
> just a few lines of the chan_unicall receiving DNIS digits:
> http://pastebin.com/HcjUvsx9
>
> Regards,
>
>
> Ing Arturo Ochoa
> Network Admin at Electrosystems
> Blog: http://arturoochoa.wordpress.com
>
>
>
>
>
> On Wed, May 26, 2010 at 8:11 AM, Moises Silva <moises.silva at gmail.com>
> wrote:
> > I can't see anything wrong with your dial plan.
> > The "User requested us to stop getting DNIS" basically means Asterisk
> says
> > getting more DNIS is not useful. Each time I get a digit, I send the
> number
> > to Asterisk and Asterisk checks the number against the dialplan, if
> adding
> > more digits do not help to match extensions, then it will ask openr2 to
> stop
> > getting DNIS.
> > So, if the telco tries to send 1234 as DNIS, but in the dialplan for that
> > circuit you only have:
> > _XX,n, ...
> > _X,n, ...
> > Then Asterisk will see that only 1 and 2 digit numbers are valid dial
> plan
> > numbers, as soon as receives DNIS 12 it will request to stop getting DNIS
> > because adding another digit will not help to match any extension.
> > I suggest you to add a very simple dial plan with only
> > _X.,1,Answer and see if that way you can get DNIS, there is probably
> > something in the extensions being included that is causing this.
> >
> > Moises Silva
> > Senior Software Engineer
> > Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R
> 9T3
> > Canada
> > t. 1 905 474 1990 x 128 | e. moy at sangoma.com
> >
> >
> > On Tue, May 25, 2010 at 5:19 PM, Arturo Ochoa <arturo.era at gmail.com>
> wrote:
> >>
> >> Thanks Moy,
> >>
> >> Well, I posted in pastebin: http://pastebin.com/ii737TtW
> >>
> >> That's just part of the context that is in charge of receiving incoming
> >> calls from the card hooked to the PBX. Normally they dial 5 digits, and
> it
> >> can be some internall SIP Exten, or maybe another exten on different
> >> Asterisk.
> >>
> >> What I don't understand is why in many other Asterisk systems plugged to
> >> Telcos for example, using OpenR2, I always received 4 digits for the
> >> incomming call (Telmex, Alestra). And it really is up to me, how to
> handle
> >> the incomming DID's,  I always have at least one Incoming route
> configured
> >> to handle all the different DID's and send it to, for example some IVR
> or
> >> whatever.
> >>
> >> Actually in this server, from the Telco perspective, I don't really care
> >> of the DNIS. The call is being answer and that's all they need. But on
> the
> >> other hand, incoming calls from the PBX, need to be routed to different
> >> places... that's the point I'm stuck with.
> >>
> >>
> >>
> >> Ing Arturo Ochoa
> >> Network Admin at Electrosystems
> >> Blog: http://arturoochoa.wordpress.com
> >>
> >>
> >>
> >>
> >> On Tue, May 25, 2010 at 2:49 PM, Moises Silva <moises.silva at gmail.com>
> >> wrote:
> >>>
> >>> This means the dialplan rules told us to stop getting DNIS. Pastebin
> the
> >>> dialplan ( just the relevant context ).
> >>>
> >>> Moises Silva
> >>> Senior Software Engineer
> >>> Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON
> L3R
> >>> 9T3 Canada
> >>> t. 1 905 474 1990 x 128 | e. moy at sangoma.com
> >>>
> >>>
> >>> On Tue, May 25, 2010 at 4:33 PM, Arturo Ochoa <arturo.era at gmail.com>
> >>> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I'd like to know if someone can give some ideas on what's going on in
> >>>> here:
> >>>>
> >>>> [15:52:50:188] [Thread: 3077299088] [Chan 62] - M - Getting DNIS digit
> 0
> >>>> [15:52:50:188] [Thread: 3077299088] [Chan 62] - M - DNIS so far: 6,
> >>>> expected length: 5
> >>>> [15:52:50:188] [Thread: 3077299088] [Chan 62] - M - User requested us
> to
> >>>> stop getting DNIS!
> >>>> [15:52:50:188] [Thread: 3077299088] [Chan 62] - M - MF Tx >> 6 [ON]
> >>>> [15:52:50:188] [Thread: 3077299088] [Chan 62] - M - scheduled timer id
> 2
> >>>> (mf_back_cycle)
> >>>>
> >>>>
> >>>> Openr2 1.3.0 with asterisk 1.4.31.
> >>>>
> >>>> 1 card connected to Alestra Telco
> >>>> 1 card connected to Ericsson PBX
> >>>>
> >>>> Every incoming call, is recevied with only 1 DNIS digit. Doesn't
> matter
> >>>> what number of DNIS digits I configure.
> >>>>
> >>>> Weird thing is that this server is being running since 3 years ago,
> but
> >>>> with the old mfcr2 release.
> >>>>
> >>>> Any Ideas?
> >>>>
> >>>> Thanks
> >>>>
> >>>>
> >>>> Ing Arturo Ochoa
> >>>> Network Admin at Electrosystems
> >>>> Blog: http://arturoochoa.wordpress.com
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> _____________________________________________________________________
> >>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >>>>
> >>>> asterisk-r2 mailing list
> >>>> To UNSUBSCRIBE or update options visit:
> >>>>   http://lists.digium.com/mailman/listinfo/asterisk-r2
> >>>
> >>>
> >>> --
> >>> _____________________________________________________________________
> >>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >>>
> >>> asterisk-r2 mailing list
> >>> To UNSUBSCRIBE or update options visit:
> >>>   http://lists.digium.com/mailman/listinfo/asterisk-r2
> >>
> >>
> >> --
> >> _____________________________________________________________________
> >> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >>
> >> asterisk-r2 mailing list
> >> To UNSUBSCRIBE or update options visit:
> >>   http://lists.digium.com/mailman/listinfo/asterisk-r2
> >
> >
> > --
> > _____________________________________________________________________
> > -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >
> > asterisk-r2 mailing list
> > To UNSUBSCRIBE or update options visit:
> >   http://lists.digium.com/mailman/listinfo/asterisk-r2
> >
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20100526/d42606b1/attachment.htm 