Generic selectors
Exact matches only
Search in title
Search in content

CAMEL

Viewing 15 posts - 1 through 15 (of 16 total)
  • Author
    Posts
  • #38195 Reply
    Andrew
    Guest

    Hi Guys,

    A bit off the topic but I wonder if you guys can help me with the following: (btw I am new to CAMEL and relatively new to Mobile Comms)

    1. CAMEL talks about O-CSI and T-CSI, where O-CSI is sent to the VLR of the visited MSC at LU and changes to O-CSI, and O and T_CSI are sent to the GMSC when it interrogates the HLR for routing info (GMSCs handle calls originating from the PSTN or other mobile networks, right ??)

    Now why is an (V)MSC not mentioned and only a GMSC mentioned in terms of receiving the O & T-CSI?

    As I understand it a call could be mobile originated and terminated and the MSC serving the MS originating the call would need to interrogate the HLR for routing info.

    Does this mean that a mobile originated call to another MS in the network will not trigger TDPs set in the T-CSI??

    2. I have a vague understanding of O-CSI and T-CSI !! could someone explain the difference between the two?

    Kind Regards

    Andrew

    #38196 Reply
    Roameo
    Guest

    Hi,
    Intresting questions.
    Let me first clarify point 2 of yours.
    O-CSI is used for MO-triggers from the VLR. So if A makes call to B A’s MSC/SSF uses O-CSI to decide whom to send the DP.This O-CSI is obtained during LU.
    B’s GMSC first fires an SRI(routing info) to get the T-CSI.
    This T-CSI is then used to fire MT-Dp’s.
    I could not figure out your 1st question though. Could you please elaborate on it?
    Cheers!
    R….

    #38197 Reply
    Andrew
    Guest

    Hi Roameo,

    Thanks for the reply. Your explanation was helpful.

    I think the T-CSI issue has been clarified (actually read another previous post)

    Let me explain:

    T-CSI DPs are triggered in the GMSC. Now the originating MSC maybe the GMSC or it may forward a call to the GMSC where any CAMEL service for the B party is triggered.

    All in all, CAMEL services are triggered if a T-CSI exists for B party.

    BTW – in later phases (maybe 3 or 4) there is a concept of VT-CSI which allow terminating CAMEL services to be invoked from the VMSC of the B party.

    Kind Regards

    Andrew

    #38198 Reply
    Andrew
    Guest

    Hi Roameo,

    Thanks for the reply. Your explanation was helpful.

    I think the T-CSI issue has been clarified (actually read another previous post)

    Let me explain:

    T-CSI DPs are triggered in the GMSC. Now the originating MSC maybe the GMSC or it may forward a call to the GMSC where any CAMEL service for the B party is triggered.

    All in all, CAMEL services are triggered if a T-CSI exists for B party.

    BTW – in later phases (maybe 3 or 4) there is a concept of VT-CSI which allow terminating CAMEL services to be invoked from the VMSC of the B party.

    Kind Regards

    Andrew

    #38199 Reply
    Hari
    Guest

    Hello Andrew,

    According to me, if you are in the local network and u get a incoming-call the T-CSI’s are not required since, you can directly access the HLR.

    Please conform the same. And also i want to know, what you got out of
    (actually read another previous post)

    My emailId is: ajs1977@indiatimes.com

    #38200 Reply
    Scot
    Guest

    Which vendor this Settings and Parameters belongs to ?

    Rgds

    #38201 Reply
    Hari
    Guest

    Hello Scot,
    I was not specific to any vendor settings and params.

    Correct me if i am wrong.

    -Thanks
    Hari

    #38202 Reply
    S.Vijay
    Guest

    O-CSI & T-CSI What is this ?

    Rgds

    #38203 Reply
    Hari
    Guest

    Hello Vijay,
    T-CSI and O-CSI are CAMEL triggers for terminating and originating calls respectively.

    When MS gets into the roaming area and MAP ( Update Location ) request will be sent from VLR to HLR, the HLR other then MS info also updates VLR with O_CSI triggers.

    Where as in case of terminating cals, the GMSC will be updated with the T_CSI embedded in Routing Info_ACK message.

    Hope this helps…………

    -Thanks
    Hari

    #38204 Reply
    S.Vijay
    Guest

    Hi HARI,

    What will be in OCSI Triggres…and How VPLMN MSC process such IN-Prepaid Calls ?

    Do you have some Docs for this ?

    Rgds

    #38205 Reply
    Hari
    Guest

    Vijay,
    According to me, OCSI will hold the kind of IN service expected by SCF, SCP may hold multiple services with different services, which required differnt triggers ( E_DP’s), so i think OCSI includes only the indication of CAMEL Support and Also service Key.

    I haven’t read any specs on this if any one can name the specs, it will be of great help………..

    #38206 Reply
    Pairote
    Guest

    Hi,
    I interasting this toppic.
    Can you explanation about function of T-CSI in CAMEL spec.?
    (It mean purpose of T-CSI)

    Best Begards

    #38207 Reply
    no-camel
    Guest

    Does anyone know the difference between VT-CSI and T-CSI?

    other than
    1. VT-CSI is in phase 3
    2. T-CSI is on HLR (GMSC)
    3. VT-CSI is downloaded to VLR (VMSC)

    Other than the above, does anyone know why you would choose one over the other for Term triggering?

    thanks

    #38208 Reply
    dennis
    Guest

    In Camel Ph 3 funcions are almost same:
    T-CSI
    Possible TDPs: Terminating Attempt Authorised; $(begin$(CAMEL3$); Detection of unsuccessful call establishment (Called subscriber busy; not reachable; no answer) $(end$(CAMEL3$)
    Possible DP criteria: basic service type, failure reason

    VT-CSI:
    Possible TDPs: Terminating Attempt Authorised; Detection of unsuccessful call establishment (Called subscriber busy; no answer)
    Possible DP criteria: basic service type, failure reason

    BUT in Camel Ph 2 only by VT-CSI you can detect and handle “Called subscriber busy; no answer”. In Cammel Ph 3 you have more flexibilty to decide where it is more suitable to handle IN service during MTC if it is in home network in GMSC or of it is in visited netw. of called subscriber.

    To older question here-
    SMS and IN – only in Camel Ph 3 and later
    (SMS-CSI, SMS State models),
    GPRS and IN – only in Camel Ph 3 and later (GPRS-CSI, GPRS state models)

    #38209 Reply
    kani
    Guest

    hi friends,

    can anyone tell me that in SSF can we use IP interface instead of E1 CAP interface. if so which CAMEL phase supports it.

    with regards,
    kani.

Viewing 15 posts - 1 through 15 (of 16 total)
Reply To: CAMEL
Your information:




<a href="" title="" rel="" target=""> <blockquote cite=""> <code> <pre class=""> <em> <strong> <del datetime="" cite=""> <ins datetime="" cite=""> <ul> <ol start=""> <li> <img src="" border="" alt="" height="" width="">