Re: [PATCH] Sender as shortnumber with CIMD2

Stipe Tolj <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization Wapme Systems AG
Message-ID <[email protected]>
"Arne K. Haaje" wrote:

> > I don't understand what's the issue here. If you send the number as 123
> > it arrives on the phone as 123, if you send it as +123 it will arrive as
> > +123. So is this not good enough??
> 
> Not it looks like the operators MC adds the + sign even when sending
> just 123.

hmm, and how do you want to avoid this then?! I don't see how.

> What the patch does is just that it treats all numerical 'from=' fields
> up to shortnumber= digits as an alphanumeric sender. This avoids the MC
> prepending the pluss sign. So if shortnumber=4 - from=2030 will be
> received without the pluss sign.

Ok, I guess I understand know what the point is. the
parm_valid_address() checks if it's an alphanumber address and that's
where you problem begins while you want to send "2030" as alphanumeric
and not numeric to avoid the prepending +.

Ok, it's a problem for you in some sence. But adding shortnumber as
smsc directive is a -1 vote IMO. You should try to solve this on
another way.

You may use the existing 'source-addr-ton' and/or 'source-addr-npi'
directives for CIMD2. This would be a better way in using "common"
directives for various SMSC module types.

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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.