- This topic is empty.
13th January 2017 at 11:46 #37837Wallis DudhnathGuest
You will need to confirm that the Roamers have CAMEL flags set in the HPLMN. You will need to check this with the HPLMN CSP. Next step is to use a protocol analyser with a trace to look at the CAP V2 and MAP messages that are exchanged between the VPLMN (your Network) and the HPLMN. There maybe a node in the signalling chain that is “filtering” the IDP. Check what SS7 Policing Masks you have on your egress routes.
VBR/ Wallis Dudhnath25th January 2017 at 13:47 #37838eleniGuest
VPLMN roaming network support CAMEL PHASE 3 and
our subscriber which perform LOCATION UPDATE in VPLMN support PHASE 2
OUR SUBSCRIBER COULD PERFORM MOC CALLS
WITH SUCCEESS OR NO ?27th January 2017 at 12:17 #37839Wallis DudhnathGuest
Location update to the VLR (VPLMN MSC/VLR) is done via MAP, e.g. MAP V3.
CAMEL is a Network Protocol that uses CAP (e.g. CAP V2/V3) and MAP (e.g. MAP V2 / V3).
Protocols have been designed to allow a degree of “auto-bauding”. MOC calls can be made.16th March 2017 at 14:15 #37840eleniGuest
prepaid subscriber has been performed LU
in vplmn network (roaming)
it could not charge for voice calls (before and after the same balance), but could charge for GPRS.
could you please help me?16th March 2017 at 15:31 #37841Wallis DudhnathGuest
For cAP V3 there is a relationship between the gprsSSF (SGSN)and the gsmSCF (SCP). This is different from the Call Control that is used to control Voice / Telephony. Check that your CAMEL node is equipped, i.e.
configured, for CAP V3 Call Control. Maybe you just have a data License implemented that
allows you to use CAP V3 for pure GPRS sessions.
VBR/ Wallis Dudhnath22nd March 2017 at 05:26 #37842Wallis DudhnathGuest
Did you check if you have Call-Control (CC) with your version of CAP V3. Assume that the configuration you have is that you will use CC your deployed MSC/VLR/gsmSSF. For GPRS, the gprsSSF will be used for pure data sessions.
VBR/ Wallis Dudhnath22nd March 2017 at 09:54 #37843ELENIGuest
Thanks for your answer
we and vplmn network support cap version2 and also
i change the camel data to msisdn number and prepaid platform is configured to
receive calls for recharge (for vplmn network)
i took the same result
before and after call credit is the same25th March 2017 at 09:15 #37844Wallis DudhnathGuest
CAP V2 has been around for a long time. The Call Flow Use Case(s) is well established for Telephony between the
gsmSSF and the gsmSCF / SDF entities.
For your “converged” Charging Prepaid platform for Voice / Data I am assuming that CAP V3 (GPRS Data) and CAP V2 is integrated onto the same platform (gsmSCF / SCP / SDF). Next step is now to look at the Tariff Plan configuration and the “buckets” that have been configured for Voice, Voice-Roaming, Data, SMS, etc..
Mediated CDRs will also help to understand what has happened with the Voice session.
VBR/ Wallis Dudhnath2nd June 2017 at 11:42 #37845raffiGuest
I want this document30th January 2018 at 10:25 #37846ELENIGuest
Inbound ROAMER Prepaid try to perform LU
to our network.
In our MSS , IDP produced (invoke initial IDP)
their Home IN answer to us (invoke establish Temporary connection)
after that we sent (return error ETC failed)
and finally the foreign network sent
thanks31st January 2018 at 11:55 #37847Wallis DudhnathGuest
Thanks Eleni. I was expecting to see DFC / AC / etc.. followed by a Connect().
Anyhow, thanks for the update.
VBR/ Wallis Dudhnath2nd February 2018 at 10:49 #37848ELENIGuest
So i can see
from my network I TAKE
(return error ETC failed)
when i try to make LU with prepaid roamer
Do you have any idea?
postpaid LU is ok
thanks!!!!!3rd February 2018 at 11:36 #37849Wallis DudhnathGuest
ETC implies that the 3GPP OCS (HPLMN) is connecting to a gsmSRF/assisting_gsmSSF.
Looks like it is trying to setup a session to send an announcement menu.
I would ask the HPLMN operator to explain their current setup with their OCS solution.
VBR/ Wallis Dudhnath
Note: OCS: Online Charging System that is used for Realtime Charging for Voice (CAP V2 / V3) and Data (Gy).