Retrieving the dest_subaddress via sms-service configuration

[Franco Mattarini]

Hello All

I'm having a problem and wondered if anyone could help me.  I need the value
of the dest_subaddress but there seems to be no parameter in the sms-service
configuration to provide this.  

I've searched through the archive of previous posts but the only reference
to dest_subadddress is this:
http://www.nabble.com/source_port%2C-source_subaddress%2C-and-dest_subaddress-issue-tf3265346.html#a9076830

The person replying advises: 

"SMS-service configurations

Table 6-9. Parameters (Escape Codes)

%p the phone number of the sender of the SMS message
%P the phone number of the receiver of the SMS message"

I can already retrieve these values, so this reply is not relevant.  I'm
using Kannel 1.4.1 on Debian, retrieved via apt and it is the binary dist. 
Can anyone tell me how to do this?  I'm hoping not to have to hack the code,
which would keep things tidy.

Regards,
Franco
-- 
View this message in context: 
http://www.nabble.com/Retrieving-the-dest_subaddress-via-sms-service-configuration-tf3770458.html#a10660103
Sent from the Kannel - User mailing list archive at Nabble.com.

Re: Retrieving the dest_subaddress via sms-service configuration

[Ben Suffolk]

Franco,

I have to admit sub address' are something I have never used, but  
thats probably because I am from the GSM world, and I think sub  
addressing is a CDMA thing?


I don't recall seeing anything in the kannel codebase to support  
them, sorry.


Out of interest can you give me an example of how sub addresses are  
used.


Ben

On 17 May 2007, at 09:16, Franco Mattarini wrote:



Hello All

I'm having a problem and wondered if anyone could help me.  I need  
the value
of the dest_subaddress but there seems to be no parameter in the  
sms-service

configuration to provide this.

I've searched through the archive of previous posts but the only  
reference

to dest_subadddress is this:
http://www.nabble.com/source_port%2C-source_subaddress%2C-and- 
dest_subaddress-issue-tf3265346.html#a9076830


The person replying advises:

"SMS-service configurations

Table 6-9. Parameters (Escape Codes)

%p the phone number of the sender of the SMS message
%P the phone number of the receiver of the SMS message"

I can already retrieve these values, so this reply is not  
relevant.  I'm
using Kannel 1.4.1 on Debian, retrieved via apt and it is the  
binary dist.
Can anyone tell me how to do this?  I'm hoping not to have to hack  
the code,

which would keep things tidy.

Regards,
Franco
--
View this message in context: http://www.nabble.com/Retrieving-the- 
dest_subaddress-via-sms-service-configuration-tf3770458.html#a10660103

Sent from the Kannel - User mailing list archive at Nabble.com.

Re: Retrieving the dest_subaddress via sms-service configuration

[Franco Mattarini]

Hi Ben

Thanks for replying.  dest_subaddress is an SMPP (3.4) optional parameter. 
In the specification, it's defined as:

"
Tag  | Value| Wireless Network Technology
dest_subaddress | 0x0203  | CDMA, TDMA
"

"The dest_subaddress parameter specifies a subaddress associated with the
destination of the message".

In this case, our supplier uses it to pass along a code that represents the
originating network of the MO.  An example:

===
2007-05-15 10:40:23 [806] [7] DEBUG: SMPP PDU 0x8195d38 dump:
2007-05-15 10:40:23 [806] [7] DEBUG:   type_name: deliver_sm
2007-05-15 10:40:23 [806] [7] DEBUG:   command_id: 5 = 0x0005
2007-05-15 10:40:23 [806] [7] DEBUG:   command_status: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   sequence_number: 1028680 = 0x000fb248
2007-05-15 10:40:23 [806] [7] DEBUG:   service_type: NULL
2007-05-15 10:40:23 [806] [7] DEBUG:   source_addr_ton: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   source_addr_npi: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   source_addr: "447X"
2007-05-15 10:40:23 [806] [7] DEBUG:   dest_addr_ton: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   dest_addr_npi: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   destination_addr: "28338"
2007-05-15 10:40:23 [806] [7] DEBUG:   esm_class: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   protocol_id: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   priority_flag: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   schedule_delivery_time: NULL
2007-05-15 10:40:23 [806] [7] DEBUG:   validity_period: NULL
2007-05-15 10:40:23 [806] [7] DEBUG:   registered_delivery: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   replace_if_present_flag: 0 =
0x
2007-05-15 10:40:23 [806] [7] DEBUG:   data_coding: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   sm_default_msg_id: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   sm_length: 17 = 0x0011
2007-05-15 10:40:23 [806] [7] DEBUG:   short_message: "07X hello"
2007-05-15 10:40:23 [806] [7] DEBUG:   source_subaddress: "447X"
2007-05-15 10:40:23 [806] [7] DEBUG:   dest_subaddress: "32F456"
2007-05-15 10:40:23 [806] [7] DEBUG: SMPP PDU dump ends.
===



Ben Suffolk wrote:
> 
> Franco,
> 
> I have to admit sub address' are something I have never used, but  
> thats probably because I am from the GSM world, and I think sub  
> addressing is a CDMA thing?
> 
> I don't recall seeing anything in the kannel codebase to support  
> them, sorry.
> 
> Out of interest can you give me an example of how sub addresses are  
> used.
> 
> Ben
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Retrieving-the-dest_subaddress-via-sms-service-configuration-tf3770458.html#a10733606
Sent from the Kannel - User mailing list archive at Nabble.com.

@ sign

[Vahid Ghafarpour]

When smsc send at sign (@) to kannel it replace it with null character how
should I fix it? why new kannel do it?

--
--Vahid Ghafarpour.
http://vahid.ghafarpour.ir/
vahid at ghafarpour dot ir
ghafarpour at gmail dot com

Re: Retrieving the dest_subaddress via sms-service configuration

[Ben Suffolk]

Franco,

Interesting, I knew it was in the specs, but had not come across any  
use for it. The source network is passed to me via TLV, but again as  
thats not a standard use its not supported in kannel.


Regards

Ben

On 22 May 2007, at 09:32, Franco Mattarini wrote:



Hi Ben

Thanks for replying.  dest_subaddress is an SMPP (3.4) optional  
parameter.

In the specification, it's defined as:

"
Tag  | Value| Wireless Network Technology
dest_subaddress | 0x0203  | CDMA, TDMA
"

"The dest_subaddress parameter specifies a subaddress associated  
with the

destination of the message".

In this case, our supplier uses it to pass along a code that  
represents the

originating network of the MO.  An example:

===
2007-05-15 10:40:23 [806] [7] DEBUG: SMPP PDU 0x8195d38 dump:
2007-05-15 10:40:23 [806] [7] DEBUG:   type_name: deliver_sm
2007-05-15 10:40:23 [806] [7] DEBUG:   command_id: 5 = 0x0005
2007-05-15 10:40:23 [806] [7] DEBUG:   command_status: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   sequence_number: 1028680 =  
0x000fb248

2007-05-15 10:40:23 [806] [7] DEBUG:   service_type: NULL
2007-05-15 10:40:23 [806] [7] DEBUG:   source_addr_ton: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   source_addr_npi: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   source_addr: "447X"
2007-05-15 10:40:23 [806] [7] DEBUG:   dest_addr_ton: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   dest_addr_npi: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   destination_addr: "28338"
2007-05-15 10:40:23 [806] [7] DEBUG:   esm_class: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   protocol_id: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   priority_flag: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   schedule_delivery_time: NULL
2007-05-15 10:40:23 [806] [7] DEBUG:   validity_period: NULL
2007-05-15 10:40:23 [806] [7] DEBUG:   registered_delivery: 0 =  
0x

2007-05-15 10:40:23 [806] [7] DEBUG:   replace_if_present_flag: 0 =
0x
2007-05-15 10:40:23 [806] [7] DEBUG:   data_coding: 0 = 0x
2007-05-15 10:40:23 [806] [7] DEBUG:   sm_default_msg_id: 0 =  
0x

2007-05-15 10:40:23 [806] [7] DEBUG:   sm_length: 17 = 0x0011
2007-05-15 10:40:23 [806] [7] DEBUG:   short_message: "07X  
hello"
2007-05-15 10:40:23 [806] [7] DEBUG:   source_subaddress:  
"447X"

2007-05-15 10:40:23 [806] [7] DEBUG:   dest_subaddress: "32F456"
2007-05-15 10:40:23 [806] [7] DEBUG: SMPP PDU dump ends.
===

RE: MT messages queue

[info.ubichip]

Hi,

Did the different SMPP account are using the same SMSC provider ?

Are you going through a router for this connection ? are you limited to NAT
port on it ?

Regards

-Original Message-
From: Djiby SY [mailto:[EMAIL PROTECTED]
Sent: lundi 21 mai 2007 20:44
To: users@kannel.org
Cc: devel Devel
Subject: MT messages queue

Hi all,

I had a problem with bearerbox this morning and I don't see the source
of the problem.
In fact all MT messages to SMPP smsc1 where queued and stored in file,
but all messages to smsc2 and smsc3 were submitted correctely.
MO messages are received correctely from smsc1, smsc2 and smsc3.

When I look the log file, there is no ERROR message and enquire_link are
sent/received correctely.

I restarted kannel then all stored MT messages  were sent to smsc1.

I don't understand why MT messages to smsc1 were queued?
and why they were sent immediately  after kannel restart?

Has someone experienced this phenomenon?


Regards
--
Djiby





  _  

Antivirus avast!  : message Sortant sain. 


Base de donnees virale (VPS) : 000742-0, 21/05/2007
Analyse le : 22/05/2007 10:59:24
avast! - copyright (c) 1988-2007 ALWIL Software.

Re: MT messages queue

[Djiby SY]

info.ubichip a écrit :

Hi,

Did the different SMPP account are using the same SMSC provider ?
  

No. I have 3 SMPP account on different smsc provider.
Are you going through a router for this connection ? 

Do you mean internet router?

are you limited to NAT
port on it ?
  

NO NAT.

Thanks
--
Djiby

Two SMSC

[Ganeshwari]

Hi All,
I am using two sms centres. One is SMPP connection for sending the
sms only ( not for receiving ).  Another one is GSM modem ( nokia12 ) for
receiving sms only ( not for sending ).  I have created the following
configuration file,


#Bearbox Configuration
group=core
admin-port=13000
admin-password=
log-file=/SMSLOGS/bearerbox.log
log-level=2
box-allow-ip="xxx.xx.xx.*"
status-password=*
smsbox-port=13001
store-file=/SMSLOGS/sms_storage
dlr-storage=internal


# FOR SMPP CONNECTION  START

group = smsc
smsc = smpp
smsc-id=smpp1
host = xxx.xxx.xxx.xx
port = 3700
receive-port = 3700
smsc-username = "xx"
smsc-password = *
system-type = "VMA"
interface-version = 34
#source-addr-ton=5
#source-addr-npi=1
sender-prefix=""
dest-addr-ton=1
dest-addr-npi=1
source-addr-autodetect=yes
log-file=/SMSLOGS/smsc.log
log-level=2
msg-id-type=0x01

NOKIA 12 SMSC Start
group=smsc
smsc = at
smsc-id = GSM1
modemtype = nokia12
device = /dev/ttyS0
log-file=/SMSLOGS/smsc_nokia12.log
log-level=0
validityperiod = 167
keepalive = 60
my-number =9986667045
#denied-smsc-id=GSM1
#allowed-smsc-id=smpp1
#preferred-smsc-id=smpp1
## NOKIA 12 SMSC End

#NOKIA 12 MODEM start
group = modems
id = nokia12
name = "Nokia 12"
detect-string = "Nokia Mobile Phone"
need-sleep = true
# keepalive-cmd = "AT+CBC;+CSQ"
# enable-mms = true
# init-string = "AT+CNMI=2,2,0,1,1"
# ###FOR NOKIA 12 MODEM end

group = smsbox
bearerbox-host = xxx.xx.xxx.xxx
smsbox-id=smsbox_1
sendsms-port = 13020
access-log =/SMSLOGS/kannel.access
log-file =/SMSLOGS/smsbox.log
log-level=2
sendsms-chars="0123456789abcdefghijklmnopqrstuvwxyz"

group=sms-service
keyword=default
post-url=
http://xxx.xx.xxx.xxx/?sender=%p&receiver=%P×tamp=%t&message=%a&epoch_time=%T&msg_id=%I
catch-all=false
concatenation=true
max-messages=0
accept-x-kannel-headers = true

group=sendsms-user
username=xxx
password=xxx
concatenation=true
max-messages=10
split-chars=" "
forced-smsc =smpp1

I have the following problems,
+  GSM modem is receiving the sms but it is saying the message
"smsbox_list empty"
+  While sending the sms, the messages need to go via smpp
connection only but some times the messages
are going via both smscs.  I need to stop this. The messages
should go only through smpp smsc.

Can any one please help me for this ??

--
Regards,
S.K.Ganeshwari.

RE: MT messages queue

[info.ubichip]

So it looks it should be a issue with one of your SMPP provider!?

Did you setup the connection timeout correctly ?

Regards

-Original Message-
From: Djiby SY [mailto:[EMAIL PROTECTED]
Sent: mardi 22 mai 2007 11:42
To: info.ubichip
Cc: users@kannel.org; 'devel Devel'
Subject: Re: MT messages queue

info.ubichip a écrit :
> Hi,
>
> Did the different SMPP account are using the same SMSC provider ?
>  
No. I have 3 SMPP account on different smsc provider.
> Are you going through a router for this connection ?
Do you mean internet router?
> are you limited to NAT
> port on it ?
>  
NO NAT.

Thanks
--
Djiby





  _  

Antivirus avast!  : message Sortant sain. 


Base de donnees virale (VPS) : 000742-1, 22/05/2007
Analyse le : 22/05/2007 15:32:12
avast! - copyright (c) 1988-2007 ALWIL Software.

Generic error: +CME ERROR: 2; using several GSM terminals with specific routing

[Robin Stephenson]

I've got a bunch (four currently, one turned off, will eventually be six or 
seven) of GSM terminals from Round Solutions hooked up via a VSCom multi-port 
serial card.  I'm running Kannel 1.4.1-2 as supplied with Ubuntu 7.04.  My 
problem is that messages via the Orange network fail like so:

2007-05-22 17:29:26 [15892] [7] DEBUG: AT2[orange]: --> AT+CPMS?^M
2007-05-22 17:29:26 [15892] [7] DEBUG: AT2[orange]: <-- +CPMS: 
"SM",0,20,"SM",0,20,"SM",0,20
2007-05-22 17:29:26 [15892] [7] DEBUG: AT2[orange]: <-- OK
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: TP-Validity-Period: 24.0 
hours
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: --> AT+CMGS=31^M
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: <-- >
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: send command status: 1
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: --> 
0031000C81447721814324A7136F79D87D2E83D661B7BBCC06C56E3A590
E
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: --> ^Z
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: <-- >
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: <-- +CME ERROR: 2
2007-05-22 17:29:52 [15892] [7] ERROR: AT2[orange]: Generic error: +CME ERROR: 2
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: send command status: -1
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: --> AT+CMGS=31^M
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: <-- >
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: send command status: 1
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: --> 
0031000C81447721814324A7136F79D87D2E83D661B7BBCC06C56E3A590
E
2007-05-22 17:29:52 [15892] [7] DEBUG: AT2[orange]: --> ^Z
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: <-- >
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: <-- +CME ERROR: 2
2007-05-22 17:29:53 [15892] [7] ERROR: AT2[orange]: Generic error: +CME ERROR: 2
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: send command status: -1
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: --> AT+CMGS=31^M
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: <-- >
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: send command status: 1
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: --> 
0031000C81447721814324A7136F79D87D2E83D661B7BBCC06C56E3A590
E
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: --> ^Z
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: <-- >
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: <-- +CME ERROR: 2
2007-05-22 17:29:53 [15892] [7] ERROR: AT2[orange]: Generic error: +CME ERROR: 2
2007-05-22 17:29:53 [15892] [7] DEBUG: AT2[orange]: send command status: -1
2007-05-22 17:29:53 [15892] [7] DEBUG: SMSC[orange]: creating DLR message
2007-05-22 17:29:53 [15892] [7] DEBUG: SMSC[orange]: DLR = 
2007-05-22 17:29:57 [15892] [7] DEBUG: AT2[orange]: --> AT+CPMS?^M
2007-05-22 17:29:57 [15892] [7] DEBUG: AT2[orange]: <-- +CPMS: 
"SM",0,20,"SM",0,20,"SM",0,20
2007-05-22 17:29:57 [15892] [7] DEBUG: AT2[orange]: <-- OK

Similarly, with O2 I get this:

2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: --> AT+CSQ^M
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: <-- +CSQ: 18,0
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: <-- OK
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: TP-Validity-Period: 24.0 hours
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: --> AT+CMGS=28^M
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: <-- >
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: send command status: 1
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: --> 
0031000C81447721814324A70F6F19681D76BBCB6C50ECA69BCD00
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: --> ^Z
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: <-- >
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: <-- +CME ERROR: 2
2007-05-22 17:33:43 [15892] [8] ERROR: AT2[o2]: Generic error: +CME ERROR: 2
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: send command status: -1
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: --> AT+CMGS=28^M
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: <-- >
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: send command status: 1
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: --> 
0031000C81447721814324A70F6F19681D76BBCB6C50ECA69BCD00
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: --> ^Z
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: <-- >
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: <-- +CME ERROR: 2
2007-05-22 17:33:43 [15892] [8] ERROR: AT2[o2]: Generic error: +CME ERROR: 2
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: send command status: -1
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: --> AT+CMGS=28^M
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: <-- >
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: send command status: 1
2007-05-22 17:33:43 [15892] [8] DEBUG: AT2[o2]: --> 
0031000C81447721814324A70F6F19681D76BBCB6C50ECA69BCD00
2007-05-22 17:33:44 [15892] [8] DEBUG: AT2[o2]: --> ^Z
2007-05-22 17:33:44 [15892] [8] DEBUG: AT2[o2]: <-- >
2007-05-22 17:33:44 [15892] [8] DEBUG: AT2[o2]: <-- +CME ERROR: 2
2007-05-22 17:33:44

removing the plus sign

[Kaneza Innocent]

Hi all

I would like to know how I can remove the + sign on the short code, rather
than having +1234 I want to have 1234 when delivered on the phone.

 

thanks

RE: @ sign

[ashwani]

Try

Alt-charset = HPROMAN8 

In your SMSC group 

 

 

 

Regards

Ashwani

 

  _  

From: Vahid Ghafarpour [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 22, 2007 2:09 PM
To: users@kannel.org
Subject: @ sign

 

When smsc send at sign (@) to kannel it replace it with null character how
should I fix it? why new kannel do it?

-- 
--Vahid Ghafarpour.
http://vahid.ghafarpour.ir/   
vahid at ghafarpour dot ir
ghafarpour at gmail dot com