- This topic has 30 replies, 1 voice, and was last updated 11 years, 2 months ago by Brother.
4th June 2006 at 07:39 #45121Muhammad Abu BakarGuest
I want to know the factors affecting the Call Answer to Seizure Ratio and CSR. Any web link or stuy documents you could point out for me?
Thanks in advance9th February 2007 at 09:37 #45122ManoGuest
Any idea about how to increase the ASR.9th February 2007 at 10:45 #45123samGuest
Yep there should be some solution to this9th February 2007 at 10:49 #45124tufailGuest
watz the threshold for ASR..
regards10th February 2007 at 08:22 #45125jugGuest
Where do we need to check for the deteriorating ASR22nd February 2007 at 04:55 #45126manoGuest
Strange No reply for this24th February 2007 at 10:11 #45127Muhammad Abu BakarGuest
I have guessed some of them. And I’m waiting for your valuable comments.
1. The called subscriber is busy.
2. Called subscriber is out of coverage range (In case of mobile…)
3. Authentication failure at IN.24th February 2007 at 16:23 #45128PixGuest
call answer to seizure ratio…
i’ve no idea what it means 🙂 is it comparable to call setup success rate (which is (100% – sdcch drop rate) x (100% – tch assignment failure rate) ) ?
regarding the CSR, possible problems are due to :
1 – poor radio quality on the sdcch channel (poor coverage, interference, trx hardware failure or signalling link issues)
2 – poor radio quality during the tch assignment phase (usually linked to hardware problem on a trx)
3 – all tch channels are already occupied (tch congestion)
4 – operation / maintenance activities on the cell (reset / lock / …)
5 – Abis failures
6 – call drop rate due to poor coverage during the call
7 – call drop rate due to failure during a handover
pix26th February 2007 at 04:08 #45129ManoGuest
Thanks Muhammed,I guess we are in the correct direction.Guess the first two points could be rectified by routing the call to announcments so that the call is actually processed.As for the third I need to research,Guess there are other reasons too
Pix,Its nothing to do with the Radio Part.Its entirely core related26th February 2007 at 07:26 #45130pixGuest
that’s why it all sounds different…28th February 2007 at 07:05 #45131Muhammad Abu BakarGuest
quote:”Its nothing to do with the Radio Part.Its entirely core related”
I think radio interface does effect the CSR. The last two points of pix are worh consideration.
Thanks pix!28th February 2007 at 07:32 #45132Muhammad Abu BakarGuest
I have come up with some more reasons for low ASR. Now I have to find details of every parameter
1. Switch Equipment Congestion
1. No Dialing in Long Time
2. No Answer in Long Time
3. No Information in Long Time
4. No Alerting in Long Time
5. Exceed Maximum Reattempt Times
6. Release before Ring
7. Release before Answer
8. Call Barring2nd March 2007 at 08:49 #45133ManoGuest
AS you pinted out reasons are many,but what matters are paramters which we have control upon.For example in the list provided by you,call barring and no answer could be straightaway eliminated since it is due to the customer behaviour.31st March 2008 at 04:44 #45134ArvinGuest
by the way ,may I know if you have an idea on how to improve an ASR for no answer issue?is there anyway we can minimize the no answer issue?Thanks.3rd April 2008 at 16:05 #45135Muhammad Abu BakarGuest
Quote: “by the way ,may I know if you have an idea on how to improve an ASR for no answer issue?is there anyway we can minimize the no answer issue?Thanks.”
I think you can! Put some penality on the subscribers for not answering 😉
Or subscriber status is updated in all switch points. So if a subscriber is unavailable, No network resources are seized. Just local switch announces subscriber unavailable…