[Home]

Summary:ASTERISK-07611: Wrong ROSE_DIVERTING_LEG_INFORMATION2 in libpri?
Reporter:Henrik Westerberg (henrikw)Labels:
Date Opened:2006-08-28 08:53:08Date Closed:2006-11-16 14:13:26.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) PBX_differences.pdf
Description:We are using asterisk-1.2.9 with a PRI line from the Swedish operator
Telia. We didn't get RDNIS into asterisk although we could se that is came in
from the operator. The problem is in the file pri_facility.h in libpri (1.2.3).

Our operator encodes divertingleginformation2 as 15 but libpri defines it as
0x15. Is this a problem with libpri or is it a problem with our operator?

These are the original defines:
/* Q.952 ROSE operations (Diverting) */
#define ROSE_DIVERTING_LEG_INFORMATION1         18
#define ROSE_DIVERTING_LEG_INFORMATION2         0x15
#define ROSE_DIVERTING_LEG_INFORMATION3         19

These are the defines that actually works:
/* Operation ID values */
/* Q.952 ROSE operations (Diverting) */
#define ROSE_DIVERTING_LEG_INFORMATION1         18
#define ROSE_DIVERTING_LEG_INFORMATION2         15
#define ROSE_DIVERTING_LEG_INFORMATION3         19

###
This is what we get from the operator:

< Facility (len=40, codeset=0) [ 0x91, 0xa1, 0x23, 0x02, 0x02, 0x00, 0x80, 0x02,
0x01, 0x0f, '0', 0x1a, 0x02, 0x01, 0x01, 0x0a, 0x01, 0x02, 0xa1, 0x12, 0xa0, 0x
10, 0xa1, 0x0e, 0x0a, 0x01, 0x02, 0x12, 0x09, '703289840' ]
< [1e 02 84 83]

###
This is the entire dump from asterisk with pri debug:

< Protocol Discriminator: Q.931 (8)  len=79
< Call Ref: len= 2 (reference 40/0x28) (Originator)
< Message type: SETUP (5)
< [a1]
< Sending Complete (len= 1)
< [04 03 90 90 a3]
< Bearer Capability (len= 5) [ Ext: 1  Q.931 Std: 0  Info transfer capability: 3
.1kHz audio (16)
<                              Ext: 1  Trans mode/rate: 64kbps, circuit-mode (16
)
<                              Ext: 1  User information layer 1: A-Law (35)
< [18 03 a1 83 8a]
< Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Preferred Dchan:
0
<                        ChanSel: Reserved
<                       Ext: 1  Coding: 0   Number Specified   Channel Type: 3
<                       Ext: 1  Channel: 10 ]
< [1c 26 91 a1 23 02 02 00 80 02 01 0f 30 1a 02 01 01 0a 01 02 a1 12 a0 10 a1 0e
0a 01 02 12 09 37 30 33 32 38 39 38 34 30]
< Facility (len=40, codeset=0) [ 0x91, 0xa1, 0x23, 0x02, 0x02, 0x00, 0x80, 0x02,
0x01, 0x0f, '0', 0x1a, 0x02, 0x01, 0x01, 0x0a, 0x01, 0x02, 0xa1, 0x12, 0xa0, 0x
10, 0xa1, 0x0e, 0x0a, 0x01, 0x02, 0x12, 0x09, '703289840' ]
< [1e 02 84 83]
< Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0) 0: 0
Location: Public network serving the remote user (4)
<                               Ext: 1  Progress Description: Calling equipment
is non-ISDN. (3) ]
< [6c 0a 21 83 31 38 31 33 34 32 35 35]
< Calling Number (len=12) [ Ext: 0  TON: National Number (2)  NPI: ISDN/Telephon
y Numbering Plan (E.164/E.163) (1)
<                           Presentation: Presentation allowed of network provid
ed number (3) '18134255' ]
< [70 05 c1 38 35 35 36]
< Called Number (len= 7) [ Ext: 1  TON: Subscriber Number (4)  NPI: ISDN/Telepho
ny Numbering Plan (E.164/E.163) (1) '8556' ]


Thanks in advance,
Henrik
Comments:By: inspired (inspired) 2006-10-23 10:36:17

Does this also solve issues with Redirecting Number on outgoing calls?
By: Henrik Westerberg (henrikw) 2006-10-31 02:00:29.000-0600

I don't know. We have a service with only incoming calls. Which issues?
By: inspired (inspired) 2006-10-31 02:41:14.000-0600

I'm connected to a Nortel DMS100 and when I set Redirecting Number (RDNIS) my calls do not go through. I received a debug from Nortel which indicates where the problem is. It is a comparison of two links, one which has Redirecting Number working, and the other ERICS01CON is us. See attached PBX_Differences.pbx
By: Henrik Westerberg (henrikw) 2006-10-31 05:49:40.000-0600

Ok, I'm not an expert on these things. Try modifing pri_facility.h and compiling libpri and see if it helps.
By: Roy Sigurd Karlsbakk (rkarlsba) 2006-11-07 06:53:14.000-0600

AFAICS this has no effect on outgoing diverted calls
By: Roy Sigurd Karlsbakk (rkarlsba) 2006-11-07 06:56:32.000-0600

It does, however, soolve setting rdnis for incoming calls, which is nice. can someone please add this to 1.2 svn?
By: Matthew Fredrickson (mattf) 2006-11-10 14:36:13.000-0600

This isn't "wrong" per se... it's just that it's different for your switch as to what it was written for originally (Q.SIG).  It's going to take some thought as to how to best do this.  For a more immediate workaround, you can change this value by hand.
By: Roy Sigurd Karlsbakk (rkarlsba) 2006-11-13 04:36:32.000-0600

I beleive this is wrong. It clearly doesn't work for several people with the current setting, so fixing it should be done anyway, and not in 1.9 or something.....
By: Matthew Fredrickson (mattf) 2006-11-14 14:02:26.000-0600

Well, the "right" fix is going to take a while, that's the fix that I personally would spend time on.  The "quick and dirty" fix is to change it by hand, or if someone else wants to write a patch that programmatically does a quick fix for this problem, that might be another way to do it.
By: Matthew Fredrickson (mattf) 2006-11-16 14:13:25.000-0600

This isn't a bug in the code per se, this is more of a feature request.  The code was originally written for Q.SIG, and the operation value is correct for that.  Someone will need to extend the interface to support more different operation values for different switchtypes.