>> Hi,
>> I was more thinking along the lines of having all TCAP users listed
>> and then "assign" ssn ranges to them. Something like:
>>
>> GSM MAP ssn[ ]
>> ANSI MAP ssn [ ]
>> RANAP ssn [ ]
>> RNSAP ssn [ ]
>> BSSAP ssn [ ]
>> CAMEL ssn [ ]
>> INAP [ ]
>> ...
>> At least you'd have them all
> Hi,
> I was more thinking along the lines of having all TCAP users
> listed and then
> "assign" ssn ranges to them. Something like:
>
> GSM MAP ssn[ ]
> ANSI MAP ssn [ ]
> RANAP ssn [ ]
> RNSAP ssn [ ]
> BSSAP ssn [ ]
> CAMEL ssn [ ]
> INAP [ ]
> ...
> At least you'd have them all in one place
ting an ANSI SSN and adding an ITU one?
Does fixing that fix your problem?
HTH,
-J
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Anders Broman
> Sent: August 22, 2006 1:10 PM
> To: 'Developer support list for Wireshark'
&g
6 6:28 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] FW: ANSI MAP / TCAP dissector hooks
>
>
> Anders Broman wrote:
>> Hi,
>> As far as I know the only change was to use range rather than a single
>> ssn value in the preferences of AN
Andreas Fink wrote:
>>> I have attached a capture file with the following:
>>>
>>> SCTP
>>> M2UA
>>> MTP3 (ITU)
>>> SCCP
>>> TCAP (ANSI)
>>> ANSI MAP
>
> I think no one expects this type of stack because ANSI MAP usually
> rides on ANSI MTP3, not ITU MTP3.
> So you obviously have a mixed case here
I have attached a capture file with the following:SCTPM2UAMTP3 (ITU)SCCPTCAP (ANSI)ANSI MAPI think no one expects this type of stack because ANSI MAP usually rides on ANSI MTP3, not ITU MTP3.So you obviously have a mixed case here which was not foreseen.Andreas FinkFink Consulting GmbH-
e...
Brg
Anders
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Michael Lum
Skickat: den 22 augusti 2006 22:28
Till: 'Developer support list for Wireshark'
Ämne: Re: [Wireshark-dev] FW: ANSI MAP / TCAP dissector hooks
I think you're right.
I had it imple
PROTECTED] On Behalf Of Anders Broman
Sent: August 22, 2006 1:10 PM
To: 'Developer support list for Wireshark'
Subject: Re: [Wireshark-dev] FW: ANSI MAP / TCAP dissector hooks
Hi,
There is a problem when ssn's overlap. I originally had ANSI MAP and GSM MAP
overlapping but still g
ld be done in TCAP instead?
Brg
Anders
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Michael Lum
Skickat: den 22 augusti 2006 22:02
Till: 'Developer support list for Wireshark'
Ämne: Re: [Wireshark-dev] FW: ANSI MAP / TCAP dissector hooks
There
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff Morriss
Sent: August 22, 2006 6:28 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] FW: ANSI MAP / TCAP dissector hooks
Anders Broman wrote:
> Hi,
> As far as I know the only change was to use range
Anders Broman wrote:
> Hi,
> As far as I know the only change was to use range rather than a single
> ssn value in the preferences of ANSI MAP, probably you got owerlaping ssn
> definitions in your preferences ( CAMEL ,GSM MAP, RANAP ... ) what does
> it say at the ssn entry in the SCCP part of th
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Michael Lum
Skickat: den 18 augusti 2006 03:40
Till: wireshark-dev@wireshark.org
Ämne: [Wireshark-dev] FW: ANSI MAP / TCAP dissector hooks
--
Michael Lum Principal Software Engineer
4600 Jacombs
--
Michael Lum Principal Software Engineer
4600 Jacombs Road+1.604.276.0055
Richmond, B.C.
Canada V6V 3B1
UTStarcom Canada, Inc.
CDMA Division
-Original Message-
From: Michael Lum [mailto:[EMAIL PROTECTED]
Sent: August 9, 2006 12:18 PM
To: 'wireshark-dev
13 matches
Mail list logo
