search

opensecure / jss7

Automatically exported from code.google.com/p/jss7
0 stars 0 forks source link

incorrect _LAYER3_IDENTIFIER in SS7 ISUP UserServiceInformation #225

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
   Send a Camel InitialDP with BearerCapability which includes UserInformationLayer 3 protocol

What is the expected output? 
   Correct decoding of the InitialDP

What do you see instead?
   ERROR [CAPServiceCircuitSwitchedCallImpl] Error processing initialDpRequest: invalid layer identifier

What version of the product are you using? On what operating system?
2.0.0.BETA3

Please provide any additional information below.

Please change in 
org.mobicents.protocols.ss7.isup.message.parameter.UserServiceInformation.java 
line 50
public static final int _LAYER3_IDENTIFIER=0x0;

to

public static final int _LAYER3_IDENTIFIER=0x3; (according to Q.931 - 4.5.5 
Bearer Capability)

Original issue reported on code.google.com by tzane...@gmail.com on 10 Jan 2013 at 1:32

GoogleCodeExporter commented 9 years ago 
Hello!

Can you please provide a pcap trace that gives this error for I will check your 
case more accurately?
You can just mail me this trace if you do not wish to share it to everybody.

Original comment by serg.vet...@gmail.com on 12 Jan 2013 at 5:57

GoogleCodeExporter commented 9 years ago 
Hello,

attached you can find an IDP trace with BearerCapability/UserInformationLayer3. 
When we try it to decode in UserServiceInformationImpl.java the switch 
statement cannot found a match an throws the IllegalArgumentException("invalid 
layer identifier")

Original comment by tzane...@gmail.com on 14 Jan 2013 at 12:49

Attachments:

GoogleCodeExporter commented 9 years ago 
Fixed in 2.1 master branch
http://code.google.com/p/jss7/source/detail?r=211f451d5f9be223a2ea1e8dc607f44702
8758dd

Original comment by serg.vet...@gmail.com on 7 Feb 2013 at 5:57

GoogleCodeExporter commented 9 years ago 
Hello!

One more updates to fix ISUP UserServiceInformation and 
cap.CalledPartyBCDNumber are here:
http://code.google.com/p/jss7/source/detail?r=211f451d5f9be223a2ea1e8dc607f44702
8758dd
http://code.google.com/p/jss7/source/detail?r=b35cb0b7edbebd38ba4653b686cc576ff7
b185cd

Thanks for a trace data that helps us much in fixing bugs.

If you can supply more trace data for ISUP/MAP/CAP this will help us to debug 
other SS7 primitives. If you are avoid to share traces to everybody you can 
just mail them to me.

Original comment by serg.vet...@gmail.com on 9 Feb 2013 at 4:27

GoogleCodeExporter commented 9 years ago

Original comment by amit.bha...@gmail.com on 3 Nov 2013 at 12:10

GoogleCodeExporter commented 9 years ago

Original comment by amit.bha...@gmail.com on 3 Nov 2013 at 12:15