Re: clarifications on xsertype 0c

[Johann Vincent Paul de Ungria Tagle]

Hi there,

Pong wrote:

This is with regard to the xser type 0c for billing.

The way I understand it, for "push" messages, we can use binfo of the 
HTTP interface.  
   

'binfo' is available in the CVS version (for emi2/sendsms).  it is not
there using 1.2.1.
Yup I'm using the CVS.

havent used the CVS version, but if there is no 'binfo' parameter
per keyword sms-service definition in kannel.conf, then
a workaround is to let your webserver do the reply by sending a 
'push message' which allows you access to the 'binfo' field =)
 

it's not in the sms-service definition.

the dirtier path (which i took) is to hardcode and use the patch below
(against 1.2.1 smsc_emi2.c) to *always* send the billing identifier
block.  just change the number of bytes in payload and set the payload 
to whatever billing codes your SMSC requires.
if the billing codes you send need to vary per keyword/service, this will 
*not* work.  just use, the 'push' trick above.
 

Thanks a lot for the code.  In the CVS smsc_emi.c there's the part where 
it makes the xser 0c if binfo exists - I put your code as an "else" 
clause to this so that it can still be overridden by binfo. =)

Thanks again!

Johann