I just said it wasn't made automatically. What part of that was unclear?
At your first answer at the thread you wrote as answer to mine question: My Q:
* I looked into a lot of docs but didn' t find any success resolution. *>*> So, how is the best way at unlang to: *>*> - convert ipaddr type to octet; *>*? - convert string to octet; *>*> - convert string to ipaddr ? *Your A: You don't. The server should automatically do this.
And then I additionally asked you, if I understood you correctly or not:
* As I understood, in case of 120 option conversion in particular is **made automatically, is it *
And it is unclear for me - "...server should automatically yes ... " , "... wasn't made automatically ..." .
* But option 43 - DHCP-Vendor is octet also. However *>>* &DHCP-Vendor = "http://user:pass@%{listen:src_ipaddr}/pbx" *>>* works fine. *> Define "works". Hint: it does the same thing as any other "octets" attribute. It takes the data you give, and dumps it into the attribute.
But why is not such situation observed with DHCP-SIP-Servers-DHCP-Option ? It is octet as well. is it because of *DHCP-Vendor* is converted by Freeradius from string to octets as well as for DHCP-SIP-Servers-DHCP-Option ? Instead it is necessary to convert it from ipaddr type to octet for right handling of DHCP-SIP-Servers-DHCP-Option ?