[ previous ] [ next ] [ threads ]
 To :  Paul Chitescu <paulc@v...>
 From :  Gamaliel Bedolla <gbf@t...>
 Subject :  Re: [yate] How to get value of second Generic Number in IAM
 Date :  Sun, 22 Jan 2012 14:36:39 -0700
Hi Paul,

Let me contact the provider, so he can edit IAM to send just one Generic
Number.
Thank you!

2012/1/22 Paul Chitescu 

> Hi!
>
> Currently the code in Yate does not support decoding or encoding more than
> one
> instance of same parameter code.
>
> Paul
>
>
> On Friday 20 January 2012 04:50:00 am Gamaliel Bedolla wrote:
> > Hi all,
> >
> > We have been working with YATE (Very nice and rich product) with SS7, and
> > it controls a cisco AS5400 GW via MGCP. The handling of outgoing and
> > incoming calls are OK. However, recently received a complaint about calls
> > to a number ringing in the main number (9454004499), when caller dialed
> > another (9455837465). We captured some traces, and we found there are two
> > Generic Number parameters in the same IAM, as show below (part of IAM) :
> >
> > Called Party Number: 9454004499
> > Pointer to start of optional part: 13
> > Calling Party Number: 7164711414
> > Charge Number: 7164211338
> > Originating line info: 0 (ANI II if < 51, reserved otherwise)
> > Generic number: 7164211338
> > Hop counter: 14
> > Generic number: 9455837465
> > End of optional parameters (0)
> >
> > And the call is routed to 9454004499
> >
> > If the IAM only has one Generic number, call is routed correctly
> > to 9455837465. This is part of a IAM (which routes call correctly):
> >
> > Called Party Number: 9454004499
> > Pointer to start of optional part: 13
> > Calling Party Number: 9453424679
> > Originating line info: 62 (ANI II if < 51, reserved otherwise)
> > Hop counter: 19
> > Generic number: 9455837465
> > Jurisdiction: 806407
> > End of optional parameters (0)
> >
> > And this is part of regexroute.conf which assigns generic number value as
> > called number:
> >
> > [from_isup]
> > ; Reject any CUG calls
> > ${isup.OptionalForwardCallIndicators}non-CUG^=if \
> > ${isup.OptionalForwardCallIndicators}CUG=-;error=facility-rejected;\
> > iisup.CauseIndicators.diagnostic=35;iisup.CauseIndicators.location=TN
> >
> > ${isup.GenericNumber.qualifier}^192$=if ${isup.GenericNumber}.=;\
> > routing=${called};called=${isup.Generic Number}
> >
> > The question is, how regexroute.conf can be configured to get the value
> of
> > the second generic number parameter, if the generic number qualifier
> always
> > is 192 (not show in the trace, but still there)?
> >
> > Please let me know if any info is needed, to find a solution to this
> issue.
> >
> > Thanks in advance.
>
>



Hi Paul,

Let me contact the provider, so he can edit IAM to send just one Generic Number.
Thank you!

2012/1/22 Paul Chitescu <paulc@v...>
Hi!

Currently the code in Yate does not support decoding or encoding more than one
instance of same parameter code.

Paul


On Friday 20 January 2012 04:50:00 am Gamaliel Bedolla wrote:
> Hi all,
>
> We have been working with YATE (Very nice and rich product) with SS7, and
> it controls a cisco AS5400 GW via MGCP. The handling of outgoing and
> incoming calls are OK. However, recently received a complaint about calls
> to a number ringing in the main number (9454004499), when caller dialed
> another (9455837465). We captured some traces, and we found there are two
> Generic Number parameters in the same IAM, as show below (part of IAM) :
>
> Called Party Number: 9454004499
> Pointer to start of optional part: 13
> Calling Party Number: 7164711414
> Charge Number: 7164211338
> Originating line info: 0 (ANI II if < 51, reserved otherwise)
> Generic number: 7164211338
> Hop counter: 14
> Generic number: 9455837465
> End of optional parameters (0)
>
> And the call is routed to 9454004499
>
> If the IAM only has one Generic number, call is routed correctly
> to 9455837465. This is part of a IAM (which routes call correctly):
>
> Called Party Number: 9454004499
> Pointer to start of optional part: 13
> Calling Party Number: 9453424679
> Originating line info: 62 (ANI II if < 51, reserved otherwise)
> Hop counter: 19
> Generic number: 9455837465
> Jurisdiction: 806407
> End of optional parameters (0)
>
> And this is part of regexroute.conf which assigns generic number value as
> called number:
>
> [from_isup]
> ; Reject any CUG calls
> ${isup.OptionalForwardCallIndicators}non-CUG^=if \
> ${isup.OptionalForwardCallIndicators}CUG=-;error=facility-rejected;\
> iisup.CauseIndicators.diagnostic=35;iisup.CauseIndicators.location=TN
>
> ${isup.GenericNumber.qualifier}^192$=if ${isup.GenericNumber}.=;\
> routing=${called};called=${isup.Generic Number}
>
> The question is, how regexroute.conf can be configured to get the value of
> the second generic number parameter, if the generic number qualifier always
> is 192 (not show in the trace, but still there)?
>
> Please let me know if any info is needed, to find a solution to this issue.
>
> Thanks in advance.