Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

Lack of MSRN

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #49820
    Sayed
    Guest

    Dear All,

    I want to know if i hav the Lack of MSRn or the Subscriber out of coverage ,is it normal to recive the same announcement for both of the case?does Cause value for both of this two case is same?

    #49821
    Sara
    Guest

    This is intresting for me as well,any one have any idea?

    #49822
    Outcast
    Guest

    What kind of equipment do ypu have?

    #49823
    Naren
    Guest

    No It shouldnt be the same…

    lack of MSRN returns SRI fail…
    Out of coverage returns Paging Fail

    #49824
    Outcast
    Guest

    If you have SRI fail, firstly you need to check your SCCP routing table. SRI goes on NP=1, NA=4, NS=XXXXX, thise number series must to be routed to HLR.

    #49825
    Naren
    Guest

    Outcast–> Please refer to the Initial Question By SAYED at the Bottom.

    #49826
    outcast
    Guest

    ok, sorry. It is possible to have the same announcement. Phrase number must be defined in EOS case, if you have E/// equipment.

    #49827
    PAN
    Guest

    Dear, Sayed

    I think, that following take place:

    1)Lack of MSRn (in VLR) —PRN_err with Cause=No Roaming Number Available—>HLR—SRI_err with Cause(most probably)=System Failure—>GMSC—appropriated announcement or ISUP_Release with Cause=111-Protocol error, unspecified—>outgoing_MSC—> appropriated announcement
    2)Subscriber out of coverage (Paging Fail in VMSC)—appropriated announcement or ISUP_Release with Cause=20-Subscriber absent—>GMSC—>outgoing_MSC—>appropriated announcement

Viewing 8 posts - 1 through 8 (of 8 total)
  • The forum ‘Telecom Design’ is closed to new topics and replies.