Bjørn Mork wrote:
> Yes, it would be. However, the document Huawei refers to does not state
> this.
Ok. So I *won't* change the dictionaries.
> I don't think footnote d leaves any doubt wrt the format of this
> attribute. The \0 prepending seems to be a Huawei invention.
Yes.
I think
Alan DeKok writes:
> lamersons wrote:
>> Thank you very much, changing it to octets gave me nice ascii look of esn.
>> Vendor is Huawei.
>
> OK.
>
>> to official letter to huawei i got this answer listed below.
>> --
>> Good day,
>>
>> I would like to inform that our BSC sen
lamersons wrote:
> Thank you very much, changing it to octets gave me nice ascii look of esn.
> Vendor is Huawei.
OK.
> to official letter to huawei i got this answer listed below.
> --
> Good day,
>
> I would like to inform that our BSC sends ESN according the
> 3GPP2 “Int
Thank you very much, changing it to octets gave me nice ascii look of esn.
Vendor is Huawei.
to official letter to huawei i got this answer listed below.
--
Good day,
I would like to inform that our BSC sends ESN according the
3GPP2 “Interoperability Specification (IOS) for c
lamersons wrote:
> I need to store ESN value to my database, but it comes in format[3GPP2-ESN =
> "\000\000\000\000\000\000\0BBF636"].
Change the dictionary to make it type "octets". That's likely the
simplest fix.
> Freeradius counts '\0' as the end
> of the line and puts blank instead of
Hi,
> I need to store ESN value to my database, but it comes in format[3GPP2-ESN =
> "\000\000\000\000\000\000\0BBF636"]. Freeradius counts '\0' as the end
> of the line and puts blank instead of actual parameter value. Not only ESN
> comes in that format but [Acct-Session-Id = "000\000"]
(debug listed below)
Freeradius 2.x
with Postgre database
I need to store ESN value to my database, but it comes in format[3GPP2-ESN =
"\000\000\000\000\000\000\0BBF636"]. Freeradius counts '\0' as the end
of the line and puts blank instead of actual parameter value. Not only ESN
comes in tha
7 matches
Mail list logo