Activity
From 08/06/2017 to 09/04/2017
08/28/2017
- 12:08 PM Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn message
- The most recent patches are now applied to osmo-msc.git master.
Instead of applying the SMPP fixes to openbsc.git'... - 11:49 AM Feature #1595: Addition of an Iu-CS interface
- IuCS now being merged to osmo-msc.git, we are able to run both 3G (IuCS) and 2G (AoIP) at the same time.
08/21/2017
- 11:49 PM Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn message
- ack that a bunch of openbsc.git patches still needs to be applied to the new osmo-*.git repositories that are relevan...
08/18/2017
- 07:42 PM Bug #2353: SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn message
- Test passes on smpp suite, but it still fails on aoip_smpp, probably because the fork of osmo-msc from osmo-nitb stil...
- 03:32 PM Bug #2353 (Feedback): SMSC: ESME sending an sms with registered_delivery=0x01 not receiving delivery_sn message
- Once openbsc patch from #2429 is merged, we can close this task.
Then patch for osmo-gsm-tester https://gerrit.osm... - 07:17 PM Bug #2429 (Resolved): SMSC: deiverSM message with bad user_message_reference
- Patch was merged and jenkins is green again. I opened a new issue in #2452 to remember to implement the missing submi...
- 10:51 AM Bug #2429 (Feedback): SMSC: deiverSM message with bad user_message_reference
- Patch available in https://gerrit.osmocom.org/#/c/3554/
We can close the issue once it's merged and osmo-gsm-teste... - 10:16 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- Sure, I'll prepare a patch probably today and add you as Reviewer.
It looks like smpp_mirror doesn't require any r... - 09:48 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- > My guess is that you didn't see these issues using smpp_mirror basically because it reuses a lot of same code which...
08/17/2017
- 04:19 PM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- the following change is needed:...
- 02:38 PM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- ...
- 09:58 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- Oh right, 8 bits :-), so yes, that should be between 0 and 255.
- 08:57 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- Thanks for pointing that out, I didn't think about it, I'll check the code of python-smpplib to see if htons() is bei...
- 08:46 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- Message reference in your pcap file is 0x0001, which is weird. This should be 0x0100 if your intention is to use refe...
08/16/2017
- 08:22 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- Hi Pablo, thanks for the pcap file. I just realized I actually attached the wrong pcap file which does not contain th...
08/14/2017
- 12:14 PM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- I'm attaching a pcap trace that you can inspect from my testbed.
- 11:59 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- > ESME sends a SUBMIT_SM message to an MS through SMSC with "Delivery receipt" enabled and
> user_message_reference=... - 09:36 AM Bug #2438 (New): MS not registered from osmocom PoV, but registered from ofono PoV
- From time to time since recently, I see some tests failing with a "Wait Timeout" while waiting for the subscriber to ...
08/13/2017
- 05:04 PM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- Yes I know we didn't support this before your patches, I actually discovered it a few weeks ago while adding SMPP tes...
08/11/2017
- 01:11 PM Bug #2433 (New): Drop MGCP_DUMMY_LOAD frames and use proper Osmux Dummy frames
In some places we are using some manually crafted dummy packets with payload = 0x23 = MGCP_DUMMY_LOAD. With latest ...- 10:44 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- I can see a Delivery Receipt is being sent in osmo-nitb.txt
^[[0;m^[[1;38m20170810122201180 DLSMS <0024> gsm_04_11...
08/10/2017
- 11:17 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- I attach pcap trace of osmo-nitb network part + GMSTAP in case it's useful.
- 10:50 AM Bug #2429: SMSC: deiverSM message with bad user_message_reference
- I attach a logfile of osmo-nitb while running that test.
- 10:37 AM Bug #2429 (Closed): SMSC: deiverSM message with bad user_message_reference
- After recent changes (most probably between 18ca1ce2ea9f0c353e6886a9d05c61238bba9dc6 and ac8ca4cfd19a23131959e88be49b...
Also available in: Atom