On the traces I have seen SMSC is tring to deliver the SMS to Norway Number +479

9013819
SRI for SM
==========
Jun
Jun
Jun
71
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
71
Jun
Jun
Jun
Jun

28 14:05:06 softmsc: 130506.736 MAP:: DialogueId:35 OPEN-REQ

28 14:05:06 softmsc:
DestAddr: RI: Route on GT. SSN:6 GT:+4799013819
28 14:05:06 softmsc:
OrigAddr: RI: Route on GT. SSN:8 GT:+4476240100
28
28
28
28
28
28
28
28
28
28
28
28
28

14:05:06
14:05:06
14:05:06
14:05:06
14:05:06
14:05:06
14:05:06
14:05:06
14:05:06
14:05:06
14:05:06
14:05:08
14:05:08

softmsc:
ApplContext: (9) 06 07 04 00 00 01 00 14 02
softmsc:
softmsc: 130506.772 MAP:: DialogueId:35 SendRoutingInfoSMReq
softmsc:
Timeout: 15
softmsc:
InvokeId: 0
softmsc:
MSISDN: +4799013819
softmsc:
SMSC: +447624010071
softmsc:
SM priority: 0
softmsc:
softmsc: 130506.794 MAP:: DialogueId:35 DELIMITER-REQ
softmsc:
softmsc: 130508.552 MAP:: DialogueId:35 OPEN-CNF
softmsc:
DestAddr: RI: Route on GT. SSN:8 GT:+4476240100

28
28
28
28

14:05:08
14:05:08
14:05:08
14:05:08

softmsc:
softmsc:
softmsc:
softmsc:

OrigAddr: RI: Route on GT. SSN:6 GT:+4790000987

Result: Accepted
ApplContext: (9) 06 07 04 00 00 01 00 14 02

We are getting the response-the location of the Subscriber(Apperently roamed to

Netherland MSC +316540851010)

Jun
Jun
Jun
Jun
Jun
Jun
Jun
10
Jun
71
Jun
Jun

28
28
28
28
28
28
28

14:05:08
14:05:08
14:05:08
14:05:08
14:05:08
14:05:08
14:05:08

softmsc: 130508.608 MAP:: DialogueId:35 SendRoutingInfoSMCnf

softmsc:
InvokeId: 0
softmsc:
MSC: +316540851010
softmsc:
IMSI: 242010978138384
softmsc:
softmsc: 130508.704 MAP:: DialogueId:36 OPEN-REQ
softmsc:
DestAddr: RI: Route on GT. SSN:8 GT:+3165408510

28 14:05:08 softmsc:
28 14:05:08 softmsc:
28 14:05:08 softmsc:

OrigAddr: RI: Route on GT. SSN:8 GT:+4476240100

ApplContext: (9) 06 07 04 00 00 01 00 15 01

SMSC Forward the Message

Jun
Jun
Jun
Jun
Jun
Jun
60
b2

28
28
28
28
28
28
82
1c

14:05:08
14:05:08
14:05:08
14:05:08
14:05:08
14:05:08
31 50 60
44 2e d3

softmsc: 130508.740 MAP:: DialogueId:36 ForwardSMReq

softmsc:
Timeout: 15
softmsc:
InvokeId: 0
softmsc:
DestAddr: 0a 00 08 42 02 01 79 18 83 83 f4
softmsc:
OrigAddr: 09 04 07 91 44 67 42 10 00 17
softmsc:
RPDU: 74 00 0b 91 51 81 23 14 07 f4 00 00 90
00 6e c8 72 9a 05 a2 97 e7 f4
e9 65 50 fb 2d 4e b3 41 67 79 39 5d 76 97 5d a0 65 d8 0d 22 d7 4

1 70 39 c3 5e 06 bd cf a0 79 d9 4d 2e 83 ca 6
9 50 bb cc 26 a7 dd 67 10 3d cd 16 87 d7 65 10 da 9e 9e 83 c8 75 90 f9 21 07 91
cb 6e 77 d9 05 5a b2 cb 6d 10 b3 9c 36 83 a6
f4 72 da 1d 96 03
We are getting MAP Abort message from the MSC-but apperantly SMS is deliverd to
the mobile.With the Abort message SMSC try to deliver the SMS again and hence mu
ltipl SMS's.
Jun
Jun
Jun
Jun
Jun
Jun
Jun
71
Jun
10
Jun
Jun

28
28
28
28
28
28
28

14:05:08
14:05:08
14:05:08
14:05:08
14:05:08
14:05:10
14:05:10

softmsc:
softmsc: 130508.762 MAP:: DialogueId:36 DELIMITER-REQ
softmsc:
softmsc: 130508.866 MAP:: DialogueId:35 CLOSE-IND
softmsc:
softmsc: 130510.173 MAP:: DialogueId:36 U-ABORT-IND
softmsc:
DestAddr: RI: Route on GT. SSN:8 GT:+4476240100

28 14:05:10 softmsc:
28 14:05:10 softmsc:
28 14:05:10 softmsc:

OrigAddr: RI: Route on GT. SSN:8 GT:+3165408510

UserReason: V1:ResourceLimit V2:ResUnavail

I don t have enough information on the traces to identify the exact reason for the
serving MSC (Netherland)to send the abort message.Probably we will do a joint t
est to identify this.