Summary: | ASTERISK-13006: [patch] !! Unknown IE 50 (cs5, Unknown Information Element) & RTCP SR transmission error, rtcp halted | ||
Reporter: | Florian Decher (fdecher) | Labels: | |
Date Opened: | 2008-11-03 07:47:17.000-0600 | Date Closed: | 2009-11-03 11:24:46.000-0600 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_dahdi/NewFeature |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) 20090515__issue13828__libpri__1.4.diff.txt ( 1) 20090515__issue13828__trunk.diff.txt ( 2) 20091004__issue13828__asterisk_trunk.diff.txt ( 3) 20091004__issue13828__libpri_1.4.diff.txt ( 4) libpri_ie50_cs5-trunk.diff3.txt | |
Description: | Hi, we have a customer running asterisk 1.4.21.2, zaptel 1.4.11, libpri 1.4.7. They are using a Digium TE 121 card. There are about 100 users working on this system. And the system is quite busy there are about 20 calls concurrent (min). Everything seems to run fine but when I connect via asterisk -r I get tons of this message (one every few seconds): RTCP SR transmission error, rtcp halted RTCP SR transmission error, rtcp halted RTCP SR transmission error, rtcp halted and I get tons of this message (one every few minutes): ! Unknown IE 50 (cs5, Unknown Information Element) the cusomer is a bit conserned about these two error messages. what are these two messages about and what should i do to get rid of them? please help me. best regards florian | ||
Comments: | By: Leif Madsen (lmadsen) 2008-11-24 14:01:17.000-0600 Can you please show the exact, full line of these log messages? Are they actually prefixed with ERROR, or is it just prefixed with WARNING or NOTICE? By: Florian Decher (fdecher) 2008-11-28 05:11:24.000-0600 Hi, these are the full lines. By: Jeff Peeler (jpeeler) 2008-12-15 15:43:49.000-0600 I think you'll find the "RTCP SR transmission error, rtcp halted" error messages go away after upgrading to at least 1.4.23 (not yet released) or anything later than 161013. Please report back if this is the case. By: Leif Madsen (lmadsen) 2009-01-27 21:03:54.000-0600 I'm going to close this out as jpeeler is pretty sure this was fixed in 1.4.23 which is now released. If this is not the case, please request this issue to be re-opened. Thanks! By: Jeff Peeler (jpeeler) 2009-01-28 09:51:52.000-0600 IE 50 seems to be an information request which I would think should be supported. Only the RTCP transmission error message would have been fixed by my change. By: Tilghman Lesher (tilghman) 2009-03-17 16:22:06 This patch should be sufficient to suppress the error. I'd be interested in seeing which type of information request was received, though. By: Tilghman Lesher (tilghman) 2009-04-28 16:29:47 fdecher: Your testing and feedback would be appreciated on this issue. By: Tilghman Lesher (tilghman) 2009-05-12 15:46:45 fdecher: ping By: Tilghman Lesher (tilghman) 2009-05-15 15:54:11 Okay, patches further implement the ability to specify the trunk accountcode in the Dial line, to be provided when the trunk requests it, in the following form: DAHDI/g1/12345678901/4444 where 4444 is the account code. By: Joshua C. Colp (jcolp) 2009-05-21 09:46:13 I've changed this issue to be a new feature now since it has turned into that. By: Leif Madsen (lmadsen) 2009-08-04 13:15:01 Changing severity to 'feature' and removing myself as the assignee since I have no hardware available to test this feature. By: Alec Davis (alecdavis) 2009-10-28 19:44:21 On our asterisk boxes connected to a Jtec QSIG card we get !! Unknown IE 50 (cs5, Unknown Information Element) Debugging with Jtec tools reveals it's Calling Party Category <pre> 0053 E1M-B 091029 12:29:09.81 Q.931 SETUP C/Ref 7CCE Org Octet 1 00000100 INFORMATION ELEMENT : Bearer Capability Octet 2 00000011 IE Length : 3 Octet 3 1------- Extension Bit : Not Continued -00----- Coding Standard : ITU-T Standard ---00000 Info Trans Capab : Speech Octet 4 1------- Extension Bit : Not Continued -00----- Transfer Mode : Circuit mode ---10000 Info Trans Rate : 64 kbit/s Octet 5 1------- Extension Bit : Not Continued -01----- Layer : User Info Layer 1 ---00011 Layer 1 Protocol : A-law (Rec G.711) Octet 1 00011000 INFORMATION ELEMENT : Channel Identification Octet 2 00000011 IE Length : 3 Octet 3 1------- Extension Bit : Not Continued -0------ Interface ID : Interface implicitly identified --1----- Interface Type : Primary Rate [or other (not Basic)] ---0---- Spare : ----1--- Preferred/Exclusive : Exclusive; only indicated channel -----0-- D Channel Indicator : Indicated channel is not the D-ch ------01 Info Channel Sel'n : As indicated in following octets Oct 3.2 1------- Extension Bit : Not Continued -00----- Coding Standard : ITU-T Standard ---0---- Number/Map : Channel is number in next octet(s) ----0011 Channel/Map Ele Type: B-channel units Oct 3.3 1------- Extension Bit : Not Continued 00000001 Channel Number : 1 Octet 1 00011110 INFORMATION ELEMENT : Progress Indicator Octet 2 00000010 IE Length : 2 Octet 3 1------- Extension Bit : Not Continued -00----- Coding Standard : ITU-T Standard ---0---- Spare : ----0001 Location : Private network serving local user Octet 4 1------- Extension Bit : Not Continued -0000011 Progress Description: Origination address is non-ISDN Octet 1 00011110 INFORMATION ELEMENT : Progress Indicator Octet 2 00000010 IE Length : 2 Octet 3 1------- Extension Bit : Not Continued -01----- Coding Standard : ISO/IEC Standard ---0---- Spare : ----0001 Location : Private network serving local user Octet 4 1------- Extension Bit : Not Continued -0010000 Progress Description: Interworking with a public network Octet 1 01101100 INFORMATION ELEMENT : Calling Party Number Octet 2 00001001 IE Length : 9 Octet 3 0------- Extension Bit : Continued -000---- Type of Number : Unknown ----0000 Numbering Plan : Unknown Octet 3a 1------- Extension Bit : Not Continued -00----- Presentation Ind'r : Presention allowed ---000-- Spare : ------00 Screening Indicator : User-provided, not screened Octet 4+ -------- Number Digits : 5604813 Octet 1 01110000 INFORMATION ELEMENT : Called Party Number Octet 2 00001010 IE Length : 10 Octet 3 1------- Extension Bit : Not Continued -000---- Type of Number : Unknown ----0000 Numbering Plan : Unknown Octet 4+ -------- Number Digits : 095551234 <b><u> Octet 1 10011101 INFORMATION ELEMENT : Non-locking Shift to Codeset 5 Octet 1 00110010 INFORMATION ELEMENT : Party Category Octet 2 00000001 IE Length : 1 Octet 3 1------- Extension Bit : Not Continued -0000--- Spare : -----000 Party Category : Unknown </u></b> where I believe the Category is from ITU Q.763 or ECMA-250 which is one of the following #define UNKNOWN_SOURCE 0x00 #define OPERATOR_FRENCH 0x01 #define OPERATOR_ENGLISH 0x02 #define OPERATOR_GERMAN 0x03 #define OPERATOR_RUSSIAN 0x04 #define OPERATOR_SPANISH 0x05 #define MUT_AGREE_CHINESE 0x06 #define MUT_AGREEMENT 0x07 #define MUT_AGREE_JAPANESE 0x08 #define NATIONAL_OPERATOR 0x09 #define ORDINARY_TOLL_CALLER 0x0a #define PRIORITY_TOLL_CALLER 0x0b #define DATA_CALL 0x0c #define TEST_CALL 0x0d #define PAY_PHONE 0x0f /* not China */ #define ORDINARY_NO_CHG 0x10 /* China only */ #define ORDINARY_PERIODIC 0x11 /* China only */ #define ORDINARY_METER_IMMED 0x12 /* China only */ #define ORDINARY_PRINTER_IMMED 0x13 /* China only */ #define PRIORITY_NO_CHG 0x14 /* China only */ #define PRIORITY_PERIODIC 0x15 /* China only */ #define ORDINARY_LOCAL 0x18 /* China only */ </pre> By: Alec Davis (alecdavis) 2009-10-28 20:26:38 Patches so far are for IE50 - Codeset 0 - INFO REQUEST. fdecher and ours are IE50 - Codeset 5, so the Info Request patches won't help us :( Needless to say, the info request patches may be useful elsewhere. By: Alec Davis (alecdavis) 2009-10-28 21:39:26 uploaded libpri_ie50_cs5-trunk.diff2.txt: And it works! < Message Type: SETUP (5) < [04 03 80 90 a3] < Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Speech (0) < Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16) < User information layer 1: A-Law (35) < [18 03 a9 83 9f] < Channel ID (len= 5) [ Ext: 1 IntID: Implicit Other(PRI) Spare: 0 Exclusive Dchan: 0 < ChanSel: As indicated in following octets < Ext: 1 Coding: 0 Number Specified Channel Type: 3 < Ext: 1 Channel: 31 Type: CPE] < [1e 02 81 81] < Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1) < Ext: 1 Progress Description: Call is not end-to-end ISDN; further call progress information may be available inband. (1) ] < [1e 02 a1 90] < Progress Indicator (len= 4) [ Ext: 1 Coding: Non-ITU international standard (1) 0: 0 Location: Private network serving the local user (1) < Ext: 1 Progress Description: Interworking with a public network. (16) ] < [6c 09 00 80 35 36 30 34 38 36 36] < Calling Number (len=11) [ Ext: 0 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) < Presentation: Presentation permitted, user number not screened (0) '5604866' ] < [70 05 80 38 36 39 39] < Called Number (len= 7) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) '8699' ] < [9d] < Non-Locking Shift (len=01): Requested codeset 5 <b><u>< [32 01 80] < Calling Party Category (len= 3) [ Ext: 1 Cat: Unknown Source (0) ] </u></b>-- Making new call for cr 99 Received message for call 0x9e07f60 on 0x9dfe2b0 TEI/SAPI 0/0, call->pri is 0x9dfe2b0 TEI/SAPI 0/0 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 30 (cs0, Progress Indicator) -- Processing IE 30 (cs0, Progress Indicator) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) <b><u>-- Processing IE 50 (cs5, Calling Party Category)</u></b> q931.c:6302 post_handle_q931_message: Call 99 enters state 6 (Call Present). Hold state: Idle Sending Receiver Ready (5) By: Richard Mudgett (rmudgett) 2009-11-02 15:15:55.000-0600 alecdavis: libpri_ie50_cs5-trunk.diff2.txt: Since code set 5 is national specific, the standards documents really need to be referenced for verification and understanding. The cpc2str() takes an integer and will supply a string from it's table when a value 0-15 is supplied. It is only called where it is given a value of 0-7. Incorrect decode is very likely because of the mismatch in field sizes expected. By: Alec Davis (alecdavis) 2009-11-02 17:11:23.000-0600 Please remove libpri_ie50_cs5-trunk.diff2.txt uploaded libpri_ie50_cs5-trunk.diff3.txt: fixed typo in dump_calling_party_category where I'd used only 3 bits instead of 4 to decode the party category. As IE50 (Codeset 5) is based on National implementations it maybe safer to not try to decode it, and just display the value? By: Leif Madsen (lmadsen) 2009-11-03 09:05:54.000-0600 Because there are a bunch of changes still going on, I'm going to drop this back to Ready for Testing for now. By: Digium Subversion (svnbot) 2009-11-03 11:24:43.000-0600 Repository: libpri Revision: 1261 U branches/1.4/pri_q931.h U branches/1.4/q931.c ------------------------------------------------------------------------ r1261 | rmudgett | 2009-11-03 11:24:42 -0600 (Tue, 03 Nov 2009) | 11 lines Unknown IE 50 (cs5, Unknown Information Element) Add code to recognize the code set 5 ie 50 (calling party category) to suppress the unknown IE message. (closes issue ASTERISK-13006) Reported by: fdecher Patches: libpri_ie50_cs5-trunk.diff3.txt uploaded by alecdavis (license 585) Tested by: alecdavis ------------------------------------------------------------------------ http://svn.digium.com/view/libpri?view=rev&revision=1261 |