Re: How can I see the TCP packages of an incoming SMS

[DHC Admin]

You can sniff USB with wireshark. But you will need an specify scenario:

https://wiki.wireshark.org/CaptureSetup/USB

On Wed, Sep 21, 2016 at 10:37 AM, Alvaro Cornejo 
wrote:

> Hi
>
> That is not possible if you use the GSM as a modem since it talks a serial
> protocol (rs232/usb), not ethernet. You might need a serial/usb sniffer.
>
> wireshark/tcpdump does "sniff" TCP packets.
>
> Regards
>
> Alvaro
>
> |---
> --|
> 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.com
>
> On Tue, Sep 20, 2016 at 6:56 PM, DHC Admin  wrote:
>
>> If you know a tcpdump would do, why don't you use it? On a linux machine
>> you would do: tcpdump -w FILENAME.pcap -s 0 host XXX.XXX.XXX.XXX (for
>> example) then use wireshark software to read the resulting file from the
>> capture.
>>
>> Once on wireshark you can search for SMPP params, like phone number.
>>
>> hope this helps.
>>
>> On Tue, Sep 20, 2016 at 5:38 PM, Manuel García Cabrera <
>> mcabr...@contentamobile.com> wrote:
>>
>>> I have a SIM inside a GSM modem (Portech mv-374), and I need to see how
>>> an incoming SMS packet is formed. A tcpdump would do, but I don't know how
>>> to obtain that. Can someone point me in the right direction?
>>>
>>>
>>>
>>
>

Re: How can I see the TCP packages of an incoming SMS

[Alvaro Cornejo]

Hi

That is not possible if you use the GSM as a modem since it talks a serial
protocol (rs232/usb), not ethernet. You might need a serial/usb sniffer.

wireshark/tcpdump does "sniff" TCP packets.

Regards

Alvaro

|-|
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.com

On Tue, Sep 20, 2016 at 6:56 PM, DHC Admin  wrote:

> If you know a tcpdump would do, why don't you use it? On a linux machine
> you would do: tcpdump -w FILENAME.pcap -s 0 host XXX.XXX.XXX.XXX (for
> example) then use wireshark software to read the resulting file from the
> capture.
>
> Once on wireshark you can search for SMPP params, like phone number.
>
> hope this helps.
>
> On Tue, Sep 20, 2016 at 5:38 PM, Manuel García Cabrera <
> mcabr...@contentamobile.com> wrote:
>
>> I have a SIM inside a GSM modem (Portech mv-374), and I need to see how
>> an incoming SMS packet is formed. A tcpdump would do, but I don't know how
>> to obtain that. Can someone point me in the right direction?
>>
>>
>>
>

RE: Load balancing MT with preferred SMSC

[Davor Spasoski]

Hi,

I realized yesterday that the reason the allowed/preferred trickery doesn’t 
work is because opensmppbox doesn’t pass smsc-id dynamically. It’s either a 
static value using the route-to-smsc directive or it’s blank if this is 
omitted. The whole point of my usecase was to have different ESMEs routed to 
different smscs and all that by using a single opensmpp instance (IP/port) due 
to specific circumstances of the case I need to solve.

AFAICS, for this to work it needs development.

BR,
Davor
Davor Spasoski
From: DHC Admin [mailto:dhcad...@gmail.com]
Sent: 21 September 2016 04:16
To: Davor Spasoski 
Cc: users@kannel.org
Subject: Re: Load balancing MT with preferred SMSC

Of course you have removed the # form those lines, right? Other than that, I 
cannot tell why it's not working for you.

On Sat, Sep 17, 2016 at 8:48 AM, Davor Spasoski 
> wrote:
Hi,

I’m trying to  use opensmppbox and kannel to act as SMPP proxy. The SMSC 
operator doesn’t allow direct connections and it has two SMSCs, one of which is 
preferred and the other handles traffic if only the preferred fails. But, both 
are always active, i.e. bearerbox is normally bound to both.
I have a dozen of ESMEs that should connect to opensmppbox with a single bind 
and then bearerbox should make two connections to smsc1 and smsc2 for each and 
every esme. To simplify, the flow with one  ESME would look like this:

    ___   _
ESME1 --> | Opensmppbox   | --> | Bearerbox |---> |SMSC1|
|   ||   |  -
|___||   |---> |SMSC2|
|___|  -

For each new ESME there would be a new set of binds from bearerbox to SMSCs and 
the system-id of the esme should distinguish the rotue in bearerbox.
Hence, use-systemid-as-smsboxid is set to true in opensmppbox.conf

At the moment, I have two fake SMSCs with same SMSC-id and they share the load 
as expected. However, no matter what I try with directives like 
preferred-smsc-id and allowed-smsc-id, I can’t make a confgiration to make 
bearerbox route all MT SMS to SMSC1 only and route to SMSC2 if only SMSC1 is 
down.

This is part of my bearerbox configuration:

group = smsc
smsc = fake
port = 12000
smsc-id = vasgw
#allowed-smsc-id = "vasgw"
#preferred-smsc-id = "vasgw"

group = smsc
smsc = fake
port = 12001
smsc-id = vasgw
#allowed-smsc-id = "vasgw"

Also, bearebox should accept MO SMS from any of the SMSC1 and SMSC2

Any ideas how to achieve this?

BR,
Davor




Disclaimer: one.Vip DOO Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system.
Please, do not print this e-mail unless it is necessary! Think about saving the 
environment!

Напомена: оне.Вип ДОО Скопје
Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде 
заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета 
пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината 
содржина, туку веднаш да ја препратите до испраќачот и да ја избришете 
оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое 
неовластено користење на оваа порака во целост или делови од истата е строго 
забрането. Ве молиме да забележите дека електронските пораки се подложни на 
промени. оне.Вип ДОО Скопје не презема одговорност за несоодветно или нецелосно 
пренесување на информациите содржани во оваа комуникација, ниту пак за било 
какво задоцнување на приемот или оштетувања на вашиот систем.
Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
природата!




Disclaimer: one.Vip DOO Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to