From: Taisto T. <go...@gm...> - 2009-10-15 14:59:19
|
Ugh OK, thanks. I hope that it will get in to the next (major) release of seagull. Do not know how to code (except small wrappers by perl), so unfortunately can not help. -Tatu Srivastava, Anuj Kumar (CMS) wrote: > HI, > > Yes this can be a feature in seagull diameter to be implemented. > Cannot comment on the time frame though. > > Regards > Anuj > > -----Original Message----- > From: Taisto Tammi [mailto:go...@gm...] > Sent: Wednesday, October 14, 2009 3:05 PM > To: Srivastava, Anuj Kumar (CMS) > Cc: gul...@li... > Subject: Re: [Seagull-users] Seagull Diameter does not understand zero data AVP? > > Ugh > > How did the re-look go? > > -Tatu > > Srivastava, Anuj Kumar (CMS) wrote: > >> Hello , >> Unfortunately I didn't have time to investigate this. >> I will have a re-look . >> >> Anuj >> >> >> >> -----Original Message----- >> From: Taisto Tammi [mailto:go...@gm...] >> Sent: Friday, September 18, 2009 3:04 PM >> To: Srivastava, Anuj Kumar (CMS) >> Cc: gul...@li... >> Subject: Re: [Seagull-users] Seagull Diameter does not understand zero data AVP? >> >> Ugh >> >> Do not want to make unnecessary hassle but this discussion did seems to stop. Would it be possible to know is this considered a bug or is it "feature" in seagull? If it is a bug could it be fixed in some time frame? >> >> -Tatu >> >> Taisto Tammi wrote: >> >> >>> Ugh >>> >>> Failed-AVP is defined in the following way: >>> >>> <define name="Failed-AVP" type="Grouped"> >>> <setfield name="avp-code" value="279"></setfield> >>> <setfield name="flags" value="64"></setfield> >>> </define> >>> >>> The Called-Station-ID is defined in following way: >>> <define name="Called-Station-Id" type="OctetString"> >>> <setfield name="avp-code" value="30"></setfield> >>> <setfield name="flags" value="64"></setfield> >>> </define> >>> >>> And OctetString and Grouped are defined like this: >>> <typedef name="OctetString" type="string" size="4" unit="octet"> >>> </typedef> <typedef name="Grouped" type="grouped"></typedef> >>> >>> Just trying to provide all the information that might be related to >>> the issue. Hope it helps. >>> >>> -Tatu >>> >>> Srivastava, Anuj Kumar (CMS) wrote: >>> >>> >>>> Hello, >>>> >>>> I guess seagull is able to handle AVPs without data in general. >>>> >>>> May be you can check the seagull dictionary how Failed-AVP is >>>> defined there ? >>>> >>>> >>>> Anuj >>>> >>>> -------------------------------------------------------------------- >>>> - >>>> --- >>>> *From:* Taisto Tammi [mailto:go...@gm...] >>>> *Sent:* Friday, August 28, 2009 5:17 PM >>>> *To:* Srivastava, Anuj Kumar (CMS) >>>> *Cc:* gul...@li... >>>> *Subject:* Re: [Seagull-users] Seagull Diameter does not understand >>>> zero data AVP? >>>> >>>> Ugh >>>> >>>> In the attachment. >>>> >>>> -Tatu >>>> >>>> Srivastava, Anuj Kumar (CMS) wrote: >>>> >>>> >>>>> Hi, >>>>> Attaching your scenario would help.. >>>>> >>>>> Anuj >>>>> >>>>> ------------------------------------------------------------------- >>>>> - >>>>> ---- >>>>> *From:* Taisto Tammi [mailto:go...@gm...] >>>>> *Sent:* Thursday, August 27, 2009 2:28 PM >>>>> *To:* gul...@li... >>>>> *Subject:* [Seagull-users] Seagull Diameter does not understand >>>>> zero data AVP? >>>>> >>>>> Ugh >>>>> >>>>> It seems that seagull, does not understand diameter AVP that have >>>>> zero data bytes. I am using seagull version 1.8.0 but I did not see >>>>> this type of bug fixed in the 1.8.1. release notes. >>>>> In my scenario seagull is acting as diameter client and there is >>>>> real diameter server in the other end, scenario is like this: >>>>> seagull -> server CER >>>>> seagull <- server CEA >>>>> seagull -> server CCR >>>>> seagull <- server CCA >>>>> >>>>> In the CCA server has put a Called-Station-Id-AVP inside of the >>>>> Failed-AVP (Grouped). The Called-Station-Id-AVP is coded in the >>>>> following way: >>>>> 00 00 00 1e ================================= AVP Code (30) >>>>> [Called-Station-Id] >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 08 ==================================== AVP Length (8) >>>>> >>>>> When the Called-Station-Id-AVP or any other AVP in that matter, is >>>>> inside of the Failed-AVP it is correct to not put data in the AVP. >>>>> This I have understand from the Diameter Base Protocol. So the >>>>> seagull must be able to validate the this type of AVP. Now it >>>>> displays an error, see a log in the in the attachments. Did also >>>>> decode manually AVPs out from the hex dump and far as I see all is >>>>> OK. Manual decode can be seen in below. >>>>> >>>>> Have I misunderstand something and there is something some way to >>>>> get this work or is this bug in the seagull? >>>>> >>>>> Manual decode of the CCA >>>>> 01 ========================================== Version 00 01 28 >>>>> ==================================== Message length 00 >>>>> ========================================== Command flags 00 01 10 >>>>> ==================================== Command-Code 00 00 00 04 >>>>> ================================= Application-Id 00 00 03 ea >>>>> ================================= Hop-by-Hop Identifier 00 00 07 d2 >>>>> ================================= End-to-End Identifier 00 00 01 07 >>>>> ================================= AVP Code (263) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 18 ==================================== AVP Length (24) >>>>> 2e 3b 31 30 ================================= AVP Data >>>>> 39 36 32 39 >>>>> 38 34 30 31 >>>>> 3b 32 30 31 >>>>> 00 00 01 08 ================================= AVP Code (264) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0f ==================================== AVP Length (15) >>>>> 48 4b 49 53 ================================= AVP Data >>>>> 43 50 34 >>>>> 00 ========================================== Padding 00 00 01 28 >>>>> ================================= AVP Code (269) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 10 ==================================== AVP Length (16) >>>>> 43 42 4f 53 ================================= AVP Data >>>>> 53 2e 46 49 >>>>> 00 00 01 a0 ================================= AVP Code (416) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 00 01 ================================= AVP Data 00 00 01 >>>>> 9f ================================= AVP Code (415) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 00 00 ================================= AVP Data 00 00 01 >>>>> 02 ================================= AVP Code (258) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 00 04 ================================= AVP Data 00 00 01 >>>>> c8 ================================= AVP Code (456) G >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 38 ==================================== AVP Length (56) >>>>> 00 00 01 af ================================= AVP Code (431) G >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 18 ==================================== AVP Length (24) >>>>> 00 00 01 a5 ================================= AVP Code (421) >>>>> 40 ========================================== AVP Flags >>>>> (M-bit) >>>>> 00 00 10 ==================================== AVP >>>>> Length >>>>> (16) >>>>> 00 00 00 00 ================================= AVP Data >>>>> 00 00 08 00 >>>>> 00 00 01 b0 ================================= AVP Code (432) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 00 19 ================================= AVP Data >>>>> 00 00 01 0c ================================= AVP Code (268) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 07 d1 ================================= AVP Data 00 >>>>> 00 >>>>> 01 c8 ================================= AVP Code (456) G >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 38 ==================================== AVP Length (56) >>>>> 00 00 01 af ================================= AVP Code (431) G >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 18 ==================================== AVP Length (24) >>>>> 00 00 01 a5 ================================= AVP Code (421) >>>>> 40 ========================================== AVP Flags >>>>> (M-bit) >>>>> 00 00 10 ==================================== AVP >>>>> Length >>>>> (16) >>>>> 00 00 00 00 ================================= AVP Data >>>>> 00 00 04 00 >>>>> 00 00 01 b0 ================================= AVP Code (432) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 00 1a ================================= AVP Data >>>>> 00 00 01 0c ================================= AVP Code (268) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 07 d1 ================================= AVP Data 00 >>>>> 00 >>>>> 01 c8 ================================= AVP Code (456) G >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 20 ==================================== AVP Length (32) >>>>> 00 00 01 b0 ================================= AVP Code (432) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 00 25 ================================= AVP Data >>>>> 00 00 01 0c ================================= AVP Code (268) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 13 a7 ================================= AVP Data *00 >>>>> 00 01 17 ================================= AVP Code (279) G >>>>> [Failed-AVP] >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 10 ==================================== AVP Length (16) >>>>> 00 00 00 1e ================================= AVP Code (30) >>>>> [Called-Station-Id]* >>>>> * 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 08 ==================================== AVP Length >>>>> (8)* 00 00 01 0c ================================= AVP Code (268) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 07 d1 ================================= AVP Data 00 00 01 >>>>> c0 ================================= AVP Code (448) >>>>> 40 ========================================== AVP Flags (M-bit) >>>>> 00 00 0c ==================================== AVP Length (12) >>>>> 00 00 01 2c ================================= AVP Data >>>>> >>>>> Br Taisto >>>>> >>>>> >>>>> |