[RFC] unified-prefix on smsc basis
Hi all, I'd like to introduce a 'unified-prefix' directive on a smsc basis that behaves the same way as the global one defines in the core group. Main intention is that smsbox does route the msg to bearerbox and bearerbox may normalize the number according to the global unified-prefix rules. But running bearerbox with dozens of various smsc connections require to map the number in different formats, which is not possible using one global unified-prefix rule set. I.e. thing of smsbox sends a msg with destination 49173... (hence in international format). Now unified-prefix convers the number to 0049173... because it's required for one EMI link. If we want to route it to an other smsc which uses SMPP with dest-addr-ton = 1, then we'd except to pass it in 49173... format. So, I guess defining the unified-prefix rules on a smsc basis is very easy to implement. BTW, I'm just coding this right now. Any comments or objections against introducing this new feature?! 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
RE: [RFC] unified-prefix on smsc basis
I'd like to introduce a 'unified-prefix' directive on a smsc basis that behaves the same way as the global one defines in the core group. have implemented it a long time ago .. was a part of my big patch .. also, actually I implemented two of them - one for incoming and another one for outgoing messages, per smsc So, I guess defining the unified-prefix rules on a smsc basis is very easy to implement. BTW, I'm just coding this right now. Any comments or objections against introducing this new feature?! I actually, don't care :) k
Re: [RFC] unified-prefix on smsc basis
At 11:58 AM 9/6/02 +0200, you wrote: So, I guess defining the unified-prefix rules on a smsc basis is very easy to implement. BTW, I'm just coding this right now. Any comments or objections against introducing this new feature?! tis very easy.. I have done this for SMPP, but not for the other smscs. We have another similar issue with sender-id. One of our providers lets one set the sender id to anything one likes as long as is prefixed by a 5digit string (probabally some account id). It might be better to do a unified-source-prefix and unified-dest-prefix. Nisan 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
Re: [RFC] unified-prefix on smsc basis
+1 for me - Original Message - From: Stipe Tolj [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 06, 2002 10:58 AM Subject: [RFC] unified-prefix on smsc basis Hi all, I'd like to introduce a 'unified-prefix' directive on a smsc basis that behaves the same way as the global one defines in the core group. Main intention is that smsbox does route the msg to bearerbox and bearerbox may normalize the number according to the global unified-prefix rules. But running bearerbox with dozens of various smsc connections require to map the number in different formats, which is not possible using one global unified-prefix rule set. I.e. thing of smsbox sends a msg with destination 49173... (hence in international format). Now unified-prefix convers the number to 0049173... because it's required for one EMI link. If we want to route it to an other smsc which uses SMPP with dest-addr-ton = 1, then we'd except to pass it in 49173... format. So, I guess defining the unified-prefix rules on a smsc basis is very easy to implement. BTW, I'm just coding this right now. Any comments or objections against introducing this new feature?! 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
