SMS SMPP Server provisioning

THE SMPP Server should have the follwoing features: SMS delivery methods: Inbound SMS options Client connect by http -> Application -> SMPP Client connect by SMPP -> Application -> SMPP DLR and MO options: when DLR arrives it should be routed back to the user (either by smpp or by http - similar to kannel for http) SMPP 'Protocol implementaiton (FULL) meaning: - Support for Unicode - Support for 7 bit - Support for 8 bit - support for UDH - support for binary SMS - Support for concat SMS smpp (outbound - client) connection options - should be full SMPP and include to define the "normal" parametes for smpp hosts: user pass host character set source ton source npi destination ton destination npi data coding schema Application should have: A. Routing capabilities: general: - Country based (prefix) primary and fallback SMS comes to the system and is send to primary GW for the country if online, if offline, then use fallback. Must support multi countrycodes (e.g. +1 and +1268) user specific:- Option to associate a user directly with ONE outbound account. B. User accounts: - Option to create application users with: user and password (valid for smpp and http connection) C. Accounting - Billing options: Must be able to extract the following from log file (user, destination country and amount of Messages per month) System Logs: - Logging of system activity outbound provider acitvity (active link, enquire, send messages) inbound user activity (activy link, enquire, send messages) - System should read User definitions in RUNNING mode, meaning that you can add a user, without restarting the system. D. System Administration: Web based administration to add users, see balances, define routings.