SMPP 3.4 Optional params

2006-06-05 Thread Leonard
Hi All, I need to set optional params on a SMPP 3.4 Bind, specifically for a bind to SimpleWire. These optional params set carrier, billing and other requirements. Is there anyway to do this with Kannel, or will I have to use their XML interface? Regards Leonard

Re: SMPP 3.4 Optional params

2006-06-05 Thread Mi Reflejo
There are no optional parameters in bind operations. (Maybe you are talking about system_type?) Kannel follows strictly SMPP specs. If you need to add any parameter which isn't in specs you should look to other way or take a look into sources by yourself :). Otherwise, if SimpleWire follows SMPP

USB Modem supported ?

2006-06-05 Thread Julien Buratto
Hello, till now I used Fastrack serial modems, but costs are getting high and serial interfaces are getting hard to find and replicators have high costs. I've found a chinese GPRS modem sold in USB with a bundled antenna - it says it supports: Tri-band EGSM900/1800/1900, GPRS multi-slot class 8,

Re: SMPP 3.4 Optional params

2006-06-05 Thread Leonard
Firstly, There are optional paramters to SMPP 3.4. - Please review the specification, or look here: http://www.alvento.com/productos/sms/smpp/smpp34.pdf section 5.3 Optional parameter are required to set carrier and billing info mation for messagin into the USA where the aggregator does not

Re: USB Modem supported ?

2006-06-05 Thread Leonard
Could not say for sure, but if it supports AT command set and is CDC-ACM complaint it should work.. (on linux box anyways.) Can you please mail me off list with the details. we require a stack of modems as well - Original Message - From: Julien Buratto [EMAIL PROTECTED] To:

Re: SMPP 3.4 Optional params

2006-06-05 Thread Mi Reflejo
If you look closer into Simplewire_SMPP_ShortCodes.pdf, optional parameters are included only in MT or MO messages (submit_sm and deliver_sm). You just need to take care sending interface_version v3.4 in bind operation. Nonetheless, kannel (as much as i know) doesn't handle optional parameters

Re: SMPP 3.4 Optional params

2006-06-05 Thread Alex Kinch
There was an Mblox patch floating around a while back that might be a good starting point for these custom parameters. Perhaps its a good time to do something a bit more permanent to the SMPP driver and the rest of Kannel so it supports the addition of carrier-specific 'optional' parameters?

Re: SMPP 3.4 Optional params

2006-06-05 Thread Leonard
Thanks Alex and Mi, This sort of work is way beyond me, as I am not a c/c++ developer by any stretch of the imagination! I, like many others reply on kannels capability to take care of this kind of thing for me. Looks like we will have to go with thier xml interface. Thanks guys. Leonard

RE: SMPP 3.4 Optional params

2006-06-05 Thread Rene Kluwen
I think Alex is right here. Optional parameters are IN the SMPP specs (at least the 3.4 version). And according to common believe in this list, SMPP specs *should* be followed as closely as possible. It shouldn't be THAT hard to add some configuration parameters that will be included as

Radius , ignoring in WAPBOX

2006-06-05 Thread cool planet
Hi Friends , I'm running kannel WAP box as my wapgateway , upto now most of implementations are success. but , when i observe the wapbox , there is one strange warning , WARNING: RADIUS: Could not find mapping for `192.168.10.100' session id 0001640622, ignoring.I dont have any

Re: SMPP 3.4 Optional params

2006-06-05 Thread Alejandro Guerrieri
You talking about TLV's right? It's a recurring issue, I think. Some operators ask for VARs to add this or that TLV to implement their custom billing module here or there and we are forced to do some terrible patch to comply with their specs. I did one once, it's not a nice job and creates