RE: AT2 sender numbers.

Thu, 29 Aug 2002 04:08:31 -0700

Ok. I don't see the log of AT receiving the PDU (only the content after decoding), but from the AT2 output this looks like a bug in both AT and AT2. I'll try to explain :
The PDU contains and "address field" which contains a "numbering plan indicator", "type of number" indicator and the actuall number. the PDU received from that certain problematic provider has the type-of-number indicator set to "network specific" and the NPI to "telex numbering scheme". now both values do not make much sense - from what I've seen, the type-of-number is set to either "international", "national" or "unkown" (that last is most often used to denote local subscribers). the NPI is usually set to either "telephone numbering plan" or "national numbering plan".
 
The AT module apparently does not take these indicators into account, while the AT2 tries to parse them and fails. who is more broken ? can't tell :-)
apparently we need to add into AT2 support for this weird setup.
 
--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]
 
+972-9-9581711 (116)
+972-67-340014
 
::..
There _is_ intelligent life on Earth, but I leave for Texas on Monday.
 

-----Original Message-----
From: Anarchy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 29, 2002 11:07 AM
To: [EMAIL PROTECTED]
Subject: RE: AT2 sender numbers.

thanks for the effort... here's the output:  

<snip> 

 Oded Arbel <[EMAIL PROTECTED]>wrote:

Actually - I would prefer to see the bearerbox log, where the driver logs the PDUs. I want to look at a pre-decoded PDU, preferably - one from the AT2 session and one from the AT session.
 
--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]
 
+972-9-9581711 (116)
+972-67-340014
 
::..
Try as much as possible to be wholly alive,
with all your might, and when you laugh,
laugh like hell and when you get angry,
get good and angry. Try to be alive.
You will be dead soon enough.
     --William Saroyan

-----Original Message-----
From: Anarchy [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 28, 2002 8:11 PM
To: [EMAIL PROTECTED]
Subject: RE: AT2 sender numbers.

it's the same regardless of whether unified-prefix is used:

unified-prefix = "+65,065,65"

from access.log:

2002-08-27 14:10:37 [4] INFO: Starting to service <keyword test> from <+9*******> to <1234>

from smsbox.log:

2002-08-27 14:10:37 Receive SMS [SMSC:] [SVC:] [ACT:] [from:+9*******] [to:1234] [flags:0:1:0:0:0] [msg:12:keyword test] [udh:0:]
2002-08-27 14:10:43 Sent SMS [SMSC:] [SVC:keyword] [ACT:] [from:13013] [to:+9*******] [flags:0:1:0:0:0] [msg:31:keyword test,******************
] [udh:0:]

it must be noted that this only happens for one of our operators.... we've tested at2 with another operator and it ran fine.... to summarise, this is what happens:

at with operator A - incoming msisdn from operator A has country code (with plus), incoming msisdn from other operators do not have country code, ok

at2 with operator A - incoming msisdn from operator A has country code (with plus), incoming msisdn from other operators do not have country code, ok

at with operator B - incoming msisdn from operator B has country code (with plus), incoming msisdn from other operators do not have country code, ok

at2 with operator B - incoming msisdn from operator B has country code (with plus), incoming msisdn from other operators do not have country code but have plus, not ok!

 Oded Arbel <[EMAIL PROTECTED]>wrote:

this is very weird. I'm currently using AT2 w/o any problem, for receiving messages from all providers. possibly you have a unified prefix that messes up the phone numbers, but this is inconsistant with the AT driver working.
Could you please send me some logs of messages being received by the AT2 module that exhibit this problem ?
 
--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]
 
+972-9-9581711 (116)
+972-67-340014
 
::..
Work is of two kinds: first, altering the position of matter at or near the earth's
surface relatively to other matter; second, telling other people to do so.
The first kind is unpleasant and ill-paid, the second is pleasant and highly paid.
 -- Bertrand Russell

-----Original Message-----
From: Anarchy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 27, 2002 2:08 PM
To: [EMAIL PROTECTED]
Subject: (no subject)

i recently started using the at2 modems group in my config and i notice that i'm not receiving some senders' number correctly... previously with the at smsc, the numbers from the local operators will either contain the country prefix with a plus  (+XXnnnnnnnn) or not at all....

however, with at2, numbers from operators other than the sim's will show up with a plus followed by the number itself (no country code, just +nnnnnnnn)... this is obviously incorrect and replies to such numbers are not possible....

the problem goes away when i switched back to at but since at is supposed to be obsolete, what gives? is this a bug or do i have to modify something like unified-prefix?

many thanks for any advice... i'm running 1.2.0 on mandrake 8.2 and my config is plain vanilla:

group = smsc
smsc = at
modemtype = wavecom
device = /dev/ttyS2

group = modems
id = wavecom
name = Wavecom
detect-string = "WAVECOM"


Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes


Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes


Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes

Reply via email to