MO Concatenation using SAR

2013-05-03 Thread Ashish Agarwal
Hello,

The SMSC is sending MO on smpp, but kannel is not able to understand the
long message, I get the following error

2013-05-03 17:44:33 [29875] [7] ERROR: SMPP[SMSC1]: sar_msg_ref_num,
sar_segment_seqnum, sar_total_segments in conjuction with UDHI used,
rejected.

Can anybody help me with configuring TLV values using SAR for proper
concatenation reassembling and forward to url?

-- 
Regards,

Ashish


Re: MO Concatenation using SAR

2013-05-03 Thread Alexander Malysh
Hi,

SMPP Spec say:

For GSM networks, the concatenation related TLVs 
(sar_msg_ref_num, sar_total_segments, sar_segment_seqnum)
or port addressing related TLVs
(source_port, dest_port) cannot be used in conjunction with 
encoded User Data Header in the short_message
(user data) field. This means that the above listed TLVs cannot 
be used if the User Data Header Indicator flag is set.

If you see such error then your SMPP-Server is buggy and send both UDHI and 
sar_. Check with your operator...

Alex

Am 03.05.2013 um 14:25 schrieb Ashish Agarwal ashisha...@gmail.com:

 Hello,
 
 The SMSC is sending MO on smpp, but kannel is not able to understand the long 
 message, I get the following error
 
 2013-05-03 17:44:33 [29875] [7] ERROR: SMPP[SMSC1]: sar_msg_ref_num, 
 sar_segment_seqnum, sar_total_segments in conjuction with UDHI used, rejected.
 
 Can anybody help me with configuring TLV values using SAR for proper 
 concatenation reassembling and forward to url?
 
 -- 
 Regards,
 
 Ashish




Unsubscribe

2013-05-03 Thread David Wachs
Stop

-Original Message-
From: Alexander Malysh amal...@kannel.org
Sent: ‎5/‎3/‎2013 8:12 AM
To: Ashish Agarwal ashisha...@gmail.com
Cc: users users@kannel.org
Subject: Re: MO Concatenation using SAR

Hi,

SMPP Spec say:

For GSM networks, the concatenation related TLVs 
(sar_msg_ref_num, sar_total_segments, sar_segment_seqnum)
or port addressing related TLVs
(source_port, dest_port) cannot be used in conjunction with 
encoded User Data Header in the short_message
(user data) field. This means that the above listed TLVs cannot 
be used if the User Data Header Indicator flag is set.

If you see such error then your SMPP-Server is buggy and send both UDHI and 
sar_. Check with your operator...

Alex

Am 03.05.2013 um 14:25 schrieb Ashish Agarwal ashisha...@gmail.com:

 Hello,
 
 The SMSC is sending MO on smpp, but kannel is not able to understand the long 
 message, I get the following error
 
 2013-05-03 17:44:33 [29875] [7] ERROR: SMPP[SMSC1]: sar_msg_ref_num, 
 sar_segment_seqnum, sar_total_segments in conjuction with UDHI used, rejected.
 
 Can anybody help me with configuring TLV values using SAR for proper 
 concatenation reassembling and forward to url?
 
 -- 
 Regards,
 
 Ashish




Re: Routing Based on Source Address

2013-05-03 Thread Alvaro Cornejo
Hi

You should be able to dfo that using allow-prefix and/or deny-prefix

Regards

Alvaro

On 5/3/13, Mike Nwaogu michael_nwa...@yahoo.com wrote:
 Hello Yall,
 Hope this meets you well and in good health.
 I'm at a crossroad in a recent development, I need to route outbound
 messages coming from my clients through an smsc_a if the source address
 matches a certain pattern and smsc_b if it doesn't as long as the
 destination address matches a certain pattern.

 123000(src_adr)|___SMSC_A

 +49***(dst_adr)|



 abc000(src_adr)|___SMSC_B

 +49***(dst_adr)|


 I'm using kannel development release v1.5.0

 How do I achieve this? The closest thing I saw in the document was the
 smsbox routing which addresses only inbound sms routing. All/Any suggestions
 would be appreciated.


 Best Regards,
 Michael C. Nwaogu


-- 
|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
  Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com



Re: Routing Based on Source Address

2013-05-03 Thread Mike Nwaogu
Thanks for getting back Alvaro, 

Yes, I tried that but it only addresses routing for the destination numbers. 
I'm trying to restrict the sender address, which in some cases are even 
alpha-numeric. Please explain further how to use allow-prefix to achieve this 
for sender address routing.

 
Best Regards,
Michael C. Nwaogu


- Original Message -
From: Alvaro Cornejo cornejo.alv...@gmail.com
To: Mike Nwaogu michael_nwa...@yahoo.com
Cc: users@kannel.org users@kannel.org
Sent: Friday, May 3, 2013 2:53 PM
Subject: Re: Routing Based on Source Address

Hi

You should be able to dfo that using allow-prefix and/or deny-prefix

Regards

Alvaro

On 5/3/13, Mike Nwaogu michael_nwa...@yahoo.com wrote:
 Hello Yall,
 Hope this meets you well and in good health.
 I'm at a crossroad in a recent development, I need to route outbound
 messages coming from my clients through an smsc_a if the source address
 matches a certain pattern and smsc_b if it doesn't as long as the
 destination address matches a certain pattern.

 123000(src_adr)|___SMSC_A

 +49***(dst_adr)|



 abc000(src_adr)|___SMSC_B

 +49***(dst_adr)|


 I'm using kannel development release v1.5.0

 How do I achieve this? The closest thing I saw in the document was the
 smsbox routing which addresses only inbound sms routing. All/Any suggestions
 would be appreciated.


 Best Regards,
 Michael C. Nwaogu


-- 
|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
              Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com