| HTTP Headers |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ |
◄ ► |
| Author | Message | |||
| Socrates Bello |
Hi, it is posible to add as HTTP Headers other parameters from the Radius accounting than the MSISDN? For example, it its posible to create a header with the informacion of the radius accounting parameter 3GPP-RAT-TYPE (Radio Access Technology used in the data session)? Best regards. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1497 Registered: 08-2008 |
Hi Socrates, Currently the only extra RADIUS attributes that we support are 3GPP_SGSN_MCC_MNC and 3GPP_SGSN_ADDRESS, which can be useful to determine whether or not a client is roaming. Do you have information on how this particular parameter is encoded? We could look at adding it to the HTTP headers, as it would not be very difficult ... unfortunately my searches show some confusion as to the proper encoding of the parameter. -- Des NowSMS Support | |||
| Socrates Bello New member Username: Socbello Post Number: 2 Registered: 04-2007 |
Hi Des, Our network nodes are Ericsson's and we have the following parameters: 3GPP-RAT-TYPE=1 (UTRAN) 3GPP-RAT-TYPE=2 (GERAN) The 3GPP-RAT-Type attribute indicates which Radio Access Technology is currently serving the UE. RAT field: Radio Access Technology type values. It shall be coded as specified in TS 29.060 [24]. RAT field is Octet String type. What is the procedure if we want to have that parameter included as a HTTP header? Ask for it to our solution provider (Volubill)? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1510 Registered: 08-2008 |
Hi Socrates, That's what is confusing ... the description says "octet string" ... but it also seems to be a single byte field. I've never seen a RADIUS feed that has this parameter set. So my question is whether the "1" is a value of hex 01, or an ASCII character "1" (hex 31). So I'm wondering if the "1" is a binary or ASCII value. Can you look at a RADIUS packet with Wireshark to see? Our dilemma is how to properly translate this parameter into an HTTP header, considering that future implementations may add additional values. It would be a good idea to route this request through Volubill. If you can provide me with this additional detail above, I'll see if I can push something through without a lot of red tape, but it would be helpful to also route the request through Volubill. -- Des NowSMS Support | |||
| Socrates Bello New member Username: Socbello Post Number: 3 Registered: 04-2007 |
Hi Des, I'm attaching a picture from Wireshark of the Radius packet. [Image Removed by User Request] I will also route the request through Volubill. Thanks for everything. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1519 Registered: 08-2008 |
Thanks Socrates, It looks like we are dealing with binary values. I'll see if I can get this into the engineering queue. -- Des NowSMS Support | |||
| Socrates Bello New member Username: Socbello Post Number: 4 Registered: 04-2007 |
OK, thanks. I already sent the request to Volubill with some traces from Wireshark. I'm waiting for their replay. Socrates. | |||
| Harsh Tak New member Username: Harshtak Post Number: 1 Registered: 05-2012 |
Moderator Note: Unrelated post moved to http://support.nowsms.com/discus/messages/131/71020.html | |||
