Re: [Seagull-users] Problem with systime into Event-Timestamp AVP

[Volker B. <VBe...@or...>]

Maybe it helps to change 
<set-value name="Event-Timestamp" method="systime" 
format="startoffset=2208988800"> </set-value> 
into 
<set-value name="Event-Timestamp" method="systime" 
format="startoffset=2208988800UL"> </set-value> 

Let me know if this works.

Volker

Massimo Galli <mas...@ho...> wrote on 29.10.2014 15:04:10:

> From: Massimo Galli <mas...@ho...>
> To: "gul...@li..." 
<gul...@li...>, 
> Date: 29.10.2014 15:05
> Subject: [Seagull-users] Problem with systime into Event-Timestamp AVP
> 
> I have a problem using systime into Event-Timestamp Diameter AVP.
> 
> In the dictionary file I define systime as:
> 
>     <external-method>
>         <defmethod name="systime" 
param="lib=lib_generalmethods.so;function=sys_time_unsig_sec">
>         </defmethod>
>     </external-method>
> 
> and I define AVP as:
> 
>             <define name="Event-Timestamp" type="Unsigned32">
>                 <setfield name="avp-code" value="55"></setfield>
>                 <setfield name="flags" value="64"></setfield>
>             </define>
> 
> The type is defined as:
> 
>         <typedef name="Unsigned32" type="number" size="4" unit="octet"> 
</typedef>
> 
> In the scenario file I define:
> 
> <set-value name="Event-Timestamp" method="systime" 
format="startoffset=2208988798"></set-value>
> 
> When I sent thw ACR message, the date/time inserted into the 
Event-Timestamp AVP is Nov 16 2012 
> 17:03:08 instead of Oct 29 2014 14:49:01. If into the Event-Timestamp I 
insert the correct value 
> instead use the systime, the data is sent correctly.
> 
> I'm not able to identify the problem ? I'm using Seagull on Windows 7 
Professional (64-bit)
> 
------------------------------------------------------------------------------
> _______________________________________________
> Gull-users mailing list
> Gul...@li...
> https://lists.sourceforge.net/lists/listinfo/gull-users


The information included in this e-mail and any files transmitted with it is strictly confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately by e-mail and delete this e-mail as well as any attachment from your system. If you are not the intended recipient you are not authorized to use and/or copy this message and/or attachment and/or disclose the contents to any other person.