TelecomSpace Discussion Forum.
December 04, 2008, 02:50:46 PM
News: Forum upgraded and more features added.
Home Help Search Login Register *
Welcome, Guest. Please login or register.
Did you miss your activation email?
December 04, 2008, 02:50:46 PM

Login with username, password and session length
Members
Total Members: 1640
Latest: phadlypah
Stats
Total Posts: 805
Total Topics: 367
Online Today: 15
Online Ever: 80
(November 22, 2008, 05:15:58 PM)
Users Online
Users: 0
Guests: 11
Total: 11
Recent posts
[Today at 02:22:19 AM]

[Yesterday at 04:02:54 AM]

by eli
[December 02, 2008, 11:07:16 PM]

by NEER
[December 02, 2008, 10:44:00 AM]

[December 01, 2008, 04:24:36 PM]

[November 30, 2008, 11:03:04 PM]

[November 28, 2008, 07:50:54 PM]

[November 28, 2008, 05:25:04 PM]

by NEER
[November 28, 2008, 08:44:41 AM]

[November 25, 2008, 08:33:38 PM]
    Pages: [1]   Go Down
    Print
    Author Topic: ForwardSM sending problem  (Read 525 times)
    firask
    Newbie
    *
    Offline Offline

    Posts: 22


    View Profile
    « on: August 25, 2008, 06:12:27 AM »

    Dear all,

    i'am trying to send MAP-MT-FORWARD-SHORT-MESSAGE-REQ or even MAP-FORWARD-SHORT-MESSAGE-REQ but there is no response is received at all from the MSC,
    i think the problem is in:

    MAPPN_sm_rp_ui ( user information ) : could any one help me with the format of this parameter what components should it be filled in it with which values ( please advice a document for it if there any ).

    OR

    should i send SRI before it. the case that i sent the SRI then i took the imsi from it and put it in the ForwardSM message but not directly, ( i took the imsi and create another message for forwardSM and put the imsi in it and send it ). is there a scenario that i should go through to receive a response...

    OR

    any other idea why there is no response from the MSC what advanced documents that could help me, or if there's any success forwardSM message trace that i could compare to my message.
    Logged
    pramod
    Newbie
    *
    Offline Offline

    Posts: 44


    View Profile
    « Reply #1 on: August 25, 2008, 08:27:27 AM »

    Hi

    Go through this doc  3GPP TS 23040 V6.8.1  for filling User Info param...

    There lots of scenarios wher MSC cant send the response if the problem still exists
    try to send the full trace of ur appln so that i can help..
    Logged
    firask
    Newbie
    *
    Offline Offline

    Posts: 22


    View Profile
    « Reply #2 on: August 26, 2008, 08:41:22 AM »

    Thanx pramod for replying Smiley
    could you give me the most known scenarios where MSC cant send the response to check it,   please ?
    i will check the document you advised for, meanwhile i hope if any one could help me more in it .

    Thanks again pramod  Wink
    Logged
    dineshonss7
    Newbie
    *
    Offline Offline

    Posts: 28


    View Profile
    « Reply #3 on: August 27, 2008, 03:23:15 AM »

    Your smsc should send SRI_SM first , so that you will know the msc id in SRI_SM_RSP of the destination number to which you have to send the Forward SM.

    Logged
    firask
    Newbie
    *
    Offline Offline

    Posts: 22


    View Profile
    « Reply #4 on: August 27, 2008, 03:40:11 AM »

    first thanks for replying
    well , what i do that i sent the SRI and get the imsi from it's response.
    and create another ForwardSM message and put the received imsi in it. and send it.
    maybe i have a problem in filling it correctly in the forwardSM.

    any suggestions???

    Thanx again dineshonss7
    Logged
    pramod
    Newbie
    *
    Offline Offline

    Posts: 44


    View Profile
    « Reply #5 on: August 27, 2008, 04:19:52 AM »

    While forming MT-ForwardSM(other Forward SM)
    check for calling ,called party addresses wher called party addr should be the MSC addr which u got from the SRI-SM response(IMSI,MSC Addr),calling party should be ur SMSC addr.


    regards
    pramod
    Logged
    firask
    Newbie
    *
    Offline Offline

    Posts: 22


    View Profile
    « Reply #6 on: August 27, 2008, 08:37:01 AM »

    well I suspected in the destination address but i think i put it right :s.

    my message is as follows:

    03 MAP-FORWARD-SHORT-MESSAGE-REQ

    0e0101  MAPPN_invoke_id

    1709040791 -destination address(MSISDN Or IMSI?)-    MAPPN_sm_rp_da

    1809040791-Originating address(MSISDN)-     MAPPN_sm_rp_oa

    1912010b0a91-destination address(MSISDN)- 0000ff04d4f29c0e00  MAPPN_sm_rp_ui

    please if you found any problem in it or any potential errors in my message to reply ASAP.

    best regards.

    Thanks in Advance Smiley
    Logged
    firask
    Newbie
    *
    Offline Offline

    Posts: 22


    View Profile
    « Reply #7 on: September 01, 2008, 03:17:29 AM »

    No suggestions?  Huh

    Sad Help Cry Help Sad Help Cry
    Logged
    pramod
    Newbie
    *
    Offline Offline

    Posts: 44


    View Profile
    « Reply #8 on: September 01, 2008, 05:23:25 AM »

    Hi
    In MT-FSM
    SM-RP-DA should be IMSI (I dont think ur filling IMSI it should be 15 digits)
    SM-RP-OA is Orig-MSISDN and  in User Info fill the Dest MSIDN, and also chek
    ur SCCP portion for calling, called party GT addresses..



    regards
    pramod

    Logged
    firask
    Newbie
    *
    Offline Offline

    Posts: 22


    View Profile
    « Reply #9 on: September 02, 2008, 12:44:31 AM »

    pramod Smiley,

    i changed my number to 15 digit IMSI,
    please clarify to me SCCP portion and called party GT addresses..

    thanks for replying  Wink
    Logged
    pramod
    Newbie
    *
    Offline Offline

    Posts: 44


    View Profile
    « Reply #10 on: September 02, 2008, 01:41:51 AM »

    Hi
     called party GT addr should be the MSC addr which u got from the SRI-SM response(IMSI,MSC Addr),calling party GT should be ur SMSC addr.

    regards
    pramod
    Logged
    firask
    Newbie
    *
    Offline Offline

    Posts: 22


    View Profile
    « Reply #11 on: September 02, 2008, 05:48:18 AM »

    Thanks pramod for your prompt response i really appreciate it.

    i put the calling party GT: I send it as follows,

    0x13 Routing on global title.

    0x_ _ _ _  my point code Point Code

    0x08 To MSC
    0x00 Translation Type
    0x12 numbering plan , encoding scheme
    0x04

    then my calling party GT
    Logged
    Pages: [1]   Go Up
    Print
    Jump to:  

    Powered by MySQL Powered by PHP Powered by SMF 1.1.3 | SMF © 2006-2007, Simple Machines LLC
    TinyPortal v0.9.7 © Bloc
    Valid XHTML 1.0! Valid CSS!
    Page created in 0.137 seconds with 26 queries.