- This topic has 11 replies, 1 voice, and was last updated 13 years ago by john.
14th February 2008 at 22:28 #51003tomGuest
my frd called me this morning but the number displayed on my cell screen was wrong. what could be the cause.15th February 2008 at 09:09 #51004scorGuest
is it within network or external network call
thks15th February 2008 at 09:57 #51005paraHOGuest
I have had that happen several times when the call is coming from mobile network to landline or vice versa.
Two instances, my sister on Vodafone network phoned on the landline and the CLI that came up was not her’s. I telephoned the CLI number that came up and the the user (a man answered) was shocked to find his number being used. He was also located in different part of country. However, the part of the country this man was located was fairly close to where my sister was located.
The second was a landline CLI that kept ringing my mobile. Eventually I rang the landline CLI and a woman answered phone. I informed her her number was ringing my mobile. She became worried as she said she had been away for several days and had onoy been back 30-minutes before my call to her landline. Spooky.
Point of interest the part of the country she was located I had been in that area some two days before folowing christmas holiday.15th February 2008 at 10:14 #51006PixGuest
The calling party number is carried in the CALL SETUP message.. but the number displayed on the called party’s screen is certainly extracted from HLR.. isn’t it ?
basically, I suspect the IN is faulty, because the display of calling party number is controlled by IN.15th February 2008 at 11:00 #51007AbdelGuest
In my experience I didn’t see a fixed line calling another fixed with a wrong CLI. because the message is carried in IAM message in SS7 or SETUP message in the PRI protocol. The problem is with the mobile network where most of the confussion comes from, call forwarding can greately effects the CLI. Sometimes, a loop of call forwarding is created and passing through dozens of trunks, some trunks have a parameter which eats away the first two digit that might be the area code, so the called can see the calling number without the area code. This is exactly what happened to a network, have you ever seen a CLI 22 OR 1. This can be avoided by a parameter in the HLR which is MAXIMUM call forwarding times. Beside, if there is a problem with the CALLING LINE IDENTIFICATION PRESENTATION(CLOP)it can also bring this problem. The function of this CLOP is to indentify to whom you are actually connecting. For example subscriber A dails subscriber B, and B is forwarded to C. After C answers the call from A the displaying number in A mobile phone is changed to subscriber C. So you can identify that B has forwarded you to C.
One day, one of my co-works was having a relationship with a girl and suddenly they broke up, and he stopped answering from her number, another guy also knew about the story, he took the mobile phone from my co-worker and he saved her number 746466 with the name 789948. That means everytime she tries to call her boyfriend number,this number 789948 displays on his phone. which he actually don’t know about this number. After he answers the call he turned back with a red face saying “its her what shall I do, I don’t wanna talk to her, by the way what happen to the mobile network. Because if he dail both numbers 746466 and 789948 the same lady will answer, I was responsible for the NSS part of our network so I checked if both numbers have some Call forwarding number activated, but there was no services. I got confused but after a long thinking I called my co-worker and told him to bring me his mobile phone and I checked the contacts menu and I found out that trick.15th February 2008 at 14:07 #51008paraHOGuest
I had a suspicion at first that this problem may be caused by congesture in network and assigning error MSRNs. Which might have meant a VLR prob.
However, since a landline number was calling me on my mobile where the person clearly said she wasn’t calling because not at home.. the MSRN point seemed wrong.
The only common factor I found here was that the mobile phones happened to be in or close to the locations where the erroneous CLIs were being generated.15th February 2008 at 20:19 #51009amcGuest
The called party number for CLI services is carried in IAM message (ISUP), but the carriers are not forced to send it, only if there´s commercial agreement for this. A call can be successful despite the wrong CLI services.16th February 2008 at 09:51 #51010PixGuest
Amc, that’s interesting. So a failure in the ISUP protocol (that’s a protocol, right?) is certainly what’s causing the trouble ?18th February 2008 at 05:35 #51011scorGuest
As Mr.Pix said the CLI is controlled not completeky by HLR but by the Gateway MSC’s wheerin the CLI can be tampered with the number of digits.The Network can be receive a call from International Network operators and route the call as a local call by using the Basic Trunks and display its own CLI.
Thks19th February 2008 at 14:22 #51012Hello Pix and ScolGuest
The CLI wrongly showed is not a failure in the ISUP protocol. The CLI service (delivery of calling party number) is based on the element configuration. When there wasn´t mobile telephony, the most of the time for international calls in Ericsson elements, it was necessary put a string into IAM, as “000000” for example, representing the calling party number when the carriers didn´t delivery the calling party number.21st February 2008 at 05:58 #51013scorGuest
the element configuration in ericsson with prefix of operators specific is for carrying out the call from ur GMSC. But the actual calling number is tampered by giving its own digits populated.
thks21st February 2008 at 16:42 #51014johnGuest
Well if routing its ok it means switching site is ok
Must check BSC side configuration