Hello Rodrigo, The API document says this about the carrier_id:
"Upon request, we can configure its system to add carrier identification on MO messages. This can be required in permium billing cases where a different price is set on different carriers, and the content provider needs the carrier identification to embed the correct price in a message. The carrier identification is passed as a string in an optional parameter rag identifier 0x1402 (carrier_id)." So I think this is about a TLV value, isn't it? I'm not really familliar with these TLV's, so I wouldn't recognise them :) Thanks. Kind regards, Roland. On 24 November 2004, 21:21:59, Rodrigo wrote: RAC> Does this carrier_id come in a TLV (Tag / Length / Value)? In such case, RAC> there is no way of getting TLV values into Kannel, and no way of setting RAC> TLV's in outgoing PDU's either. Optional parameters are not implemented into RAC> Kannel, although they are parsed and logged. But it would be an interesting RAC> thing to do. RAC> More info on TLV's: look for SMPP ver.3.4 specification.
