Hi list, I have added a 'binfo' to the Msg sms structure to pass arbitrary billing identifier/information for MT and MO messages.
In EMI2 we forward the XSer 0c field and in SMPP we forward the service_type from the deliver_sm. For MO, we have now a '%B' escape code for the sms-service to pass this binfo field into any HTTP requests and for MT we have a 'binfo' CGI variable in the sendsms interface. Beware that Kannel does only proxy those fields and does not handle any semantics associated with the billing identifier/information. The external HTTP application is in charge to "know" what to do and how to handle these information. Can anyone who feels this can be addopted to CIMD2 and OIS (or other SMSC modules) please provide patches?! Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 40470 D�sseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
