You are here

Connect B party to resource

20 posts / 0 new
Last post
alaash
Connect B party to resource

I need to create the service that does the following :
When A party calls B party B party and when B party answers, will hear an announcement before resuming the call

When the call takes place, SSP will send IDP to the SCP, I will then need to Connect B party to an IVR to hear an announcement then continue normally with the call.
I was thinking about using EstablishTemporaryConnection or ConnectToResource.
Which one should be used? and how will i be able to let only the B party hear the announcement not the A party?
Thanks in advance.

mlntdrv
mlntdrv's picture
that's a tricky one

Hi,

I think you need to use CAPv4. When you receive the MO IDP, don't send CON/CUE, instead send ICA+ETC/CTR+PA for the B party to play him the announcement. After the playing is over, you can Move Leg B to the main call segment with ML+CWA.

Cheers!

alaash
Hi mlntdrv ,

Hi mlntdrv ,

Sending ETC this way will play the announcement for the A party. Is there a way to allow the B party to hear an announcement after answering then continue the call as normal. triggering IDP on the MT call then sending ETC/CTR on call answer event will achieve that for B party ?

mlntdrv
mlntdrv's picture
No, with CAPv4 and ICA to #B

No, with CAPv4 and ICA to #B party, the #B party will be created in a separate call segment, which you can connect to resource. This segment will be separated from the main call segment (where #A party is), so #A party won't hear the announcement.

alaash
Hi

What if the switch doesn't support CAP v4 or inap cs2 , if i get the trigger IDP on the TCSI of the #B party (on incomming call for #B party. MT) and then send ETC/CTR when # B party answers , who will hear the announcement.( NO ICA is sent here).

mlntdrv
mlntdrv's picture
Umm, you cannot send ETC on T

Umm, you cannot send ETC on T_Answer. When the #B party answers, the switch will normally connect the two legs, if CAPv4 is not used.

alaash
How can i then play an

How can i then play an announcement to the #B party after he answers without using CAP v4. I am trying to create a collect call service flow without using CAP v4 ?
My main flow was to use isup loopback to connect the calls , and CAP ETC on T-answer to play the announcement.

mlntdrv
mlntdrv's picture
Do you have any access and

Do you have any access and control over the ISUP circuits in the MSC or MSS?

alaash
Yes i can handle the ISUp

Yes i can handle the ISUp traffic for the call. Is there a way to do that only using ISUP ?

mlntdrv
mlntdrv's picture
Well it is possible, but will

Well it is possible, but will look architecturally ugly :) Here's an idea: You can route all your collect calls to your assisting MSC, behind this MSC will be your gsmSCF/gsmSSF hybrid with the service on it. So, when the MO IDP comes, you will play an announcement to #A party in the standard way, then send an IAM for #B party. When #B party answers, you can instruct the Assisting MSC to play the announcement to him and then connect the two legs.

alaash
How to instruct the MSC to

How to instruct the MSC to play the announcement for # B party ? using CAMel , if yes what messages.
Do you have a flow for ISUP and CAP messages for this solution so i can understand it better ?

mlntdrv
mlntdrv's picture
Regarding "How to instruct

Regarding "How to instruct the MSC to play the announcement for # B party ?" - it is not part of the CAMEL standards, it is just the Control plane (Media Gateway controller in the MSC) sending commands to the User plane (Media Gateway). This is when split-MSC architecture is used.
Your service will act as the MGC, controlling the MGW in the Assisting MSC.
Can you accomplish this with the tools you have?

alaash
Can you provide more details

Can you provide more details about how my system will interface with the MGW. A flow would help.

alaash
i have little experience in

i have little experience in MGC and split-MSC architecture. What protocols are used to accomplish that ?

mlntdrv
mlntdrv's picture
http://en.wikipedia.org/wiki

http://en.wikipedia.org/wiki/Mobile_switching_centre_server
"The MSC Server is standards-based and communicates with other distributed elements using industry open standards such as media gateway control protocol, megaco/H.248, etc."
I don't have any flows though, the choice of the above protocols are vendor specific.

NutishAlwan
I don't think there is any

I don't think there is any gsm provider may accept to connect others platform to manage their bearer resources via H.248,if you connect to their MGW then you can cause so many problems for their bearer resources such as silent call and disconnect their request.

alaash
This is True. The thing is

This is True. The thing is that i know that some providers provide collect call using INAP CS1+ for signaling and Diameter for charging. But still i don't know the procedure and call flow for such service and how to allow the B party to hear the announcement using INAP CS1+.Any Ideas ?

alaash
Is it Possible to use ICA

Is it Possible to use ICA message and the N-CSI message to solve this ?

NutishAlwan
Are you going to implement called number is pay for the call?

Are you going to implement called number is pay for the call?if yes, the MSC will trigger N-CSI(DP2) then you will trigger the SCP after you change over the calling and the called ,in this way you will be able to use ETC message to connect the B number to to announcement.

alaash
Yes the Solution is for a

Yes the Solution is for a collect call system. DO you have more details about the flow you proposed. How can the NCSI trigger be set ?