[asterisk-dev] Diverting Leg Information 2. Original called number.

Richard Mudgett rmudgett at digium.com
Tue May 31 12:16:17 CDT 2011


> I need libpri developers suggestion.
> 
> Upperlaid Switch do not accept Facility with DivertingLegInformation2
> from Asterisk.
> The reason is: The Called number present as the Numbuer (Ox80) not as
> the Numeric String (0x12) by ETSI recomendations.
> 
> > Context Specific [0 0x00] <80> Len:9 <09>
> > <36 37 34 30 31 37 32 35-36> - "674017256"
> > ASN.1 end

Please supply the complete decode of the facility ie.

> ....
> >  > Facility (len=34, codeset=0) [ 0x91, 0xA1, 0x1D, 0x02, 0x01,
> >  > 0x0E,
> > 0x02, 0x01, 0x0F, '0',
> > 0x15, 0x02, 0x01, 0x01, 0x0A, 0x01, 0x01, 0xA1, 0x0D, 0xA0, 0x0B,
> > 0x80,
> > 0x09, '674017256'
> 
> I'm not an expert in a ETSI recommendations. However, I'm completely
> sure I have to fix it in libpri myself. Nobody going to do iton the
> switch.
> 
> I look at the source rose_enc_etsi_DivertingLegInformation2_ARG
> 
> I's look like no a simple way to encode the number as the Numeric
> String
> from roseEtsiDivertingLegInformation2_ARG structure. My be I miss
> something?

Without manually decoding, it looks like the Upperlaid Switch
is not surrounding the original called number with enough encapsulation.
You should be able to use lower level routines to encode what you need.

Richard



More information about the asterisk-dev mailing list