Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Asterisk symbol is prefixing the caller ID on transit calls

Status
Not open for further replies.

kevin906

MIS
Aug 4, 2006
167
US
System has PSS1V2 QSIG tieline from Cisco--these are the only trunks in and out of the system in question.
User is routing a number offsite after hours to answering service.
Caller ID inbound is OK.
Caller ID outbound is prefixed with * character.
The forwarding step is prefixing the caller ID with a * character.
I have been working on Hipath/Hicom systems for years and have never run into this.
Not sure where in the configuration this could be happening.
I have checked the usual suspects--KNFOR-KNDEF-KNMAT-KNPRE, nothing jumping out at me.
The called number is prefixed with 9 as it has to reach the PSTN from Cisco.

I have edited the caller ID for privacy.

Incoming CR4A09 (Q.931) (Orig) TYPE: SETUP
IE: 1 ( 3) : (04) Bearer Capability
80 90 A2
CCITT Speech, u-law
IE: 2 ( 3) : (18) Channel identification
A9 83 81
B-channel number 1
The channel is exclusive
IE: 3 (30) : (1C) QSIG facility
9F AA 06 80 01 00 82 01 00 A1 13 02 01 21 02 01
00 80 0B 55 6E 61 76 61 69 6C 61 62 6C 65
Networking Extension
Network Facility Extensions
Entity - Source: endPinx, Dest: endPinx,
Invoke
InvokeComp - ID: 21
Component type: Local value
Operation: ISO_CALLING_NAME (0)
Presentation Allowed
"Unavailable"
IE: 4 (12) : (6C) Calling party number
00 80 32 35 33 32 35 32 33 31 38 38
Unknown, Unknown, Present. allowed, User provided
713XXXXXXX
IE: 5 ( 5) : (70) Called party number
80 37 38 30 39
Unknown, Unknown
7809


Outgoing CR0008 (Q.931) (Orig) TYPE: SETUP
IE: 1 ( 0) : (A1) Sending complete
IE: 2 ( 3) : (04) Bearer Capability
80 90 A2
CCITT Speech, u-law
IE: 3 ( 3) : (18) Channel identification
A9 83 90
B-channel number 16
The channel is exclusive
IE: 4 (34) : (1C) QSIG facility
9F AA 06 80 01 00 82 01 00 8B 01 02 A1 14 02 02
A6 BE 02 01 3B 30 0B 30 09 0A 01 05 0A 01 03 0A
Networking Extension
Network Facility Extensions
Entity - Source: endPinx, Dest: endPinx,
InterpreApdu: rejectAnyUnrecogInvokePdu
Invoke
InvokeComp - ID: A6BE
Component type: Local value
Operation: ISO_CHARGE_REQUEST (59)
IE: 5 (29) : (1C) QSIG facility
9F AA 06 80 01 00 82 01 00 8B 01 00 A1 0F 02 02
A6 CD 02 01 55 30 06 82 04 06 40 08 40
Networking Extension
Network Facility Extensions
Entity - Source: endPinx, Dest: endPinx,
InterpreApdu: discardAnyUnrecogInvokePdu
Invoke
InvokeComp - ID: A6CD
Component type: Local value
Operation: CMN_INFORM (85)
Feature Identifiers:
ssCOsupported (Bit:5) - Call Offer Supported
ssAOCsupportChargeRateProvAtGatewPinx (Bit:9) - Advice Of Charge
IE: 6 (39) : (1C) QSIG facility
9F AA 06 80 01 00 82 01 00 8B 01 00 A1 19 02 02
A6 DC 02 01 00 A1 10 04 0B 55 6E 61 76 61 69 6C
Networking Extension
Network Facility Extensions
Entity - Source: endPinx, Dest: endPinx,
InterpreApdu: discardAnyUnrecogInvokePdu
Invoke
InvokeComp - ID: A6DC
Component type: Local value
Operation: ISO_CALLING_NAME (0)
Presentation Allowed
"Unavailable"
IE: 7 (13) : (6C) Calling party number
21 80 2A 32 35 33 32 35 32 33 31 38 38
National, ISDN, Present. allowed, User provided
*713XXXXXXX
IE: 8 (13) : (70) Called party number
A1 39 31 38 33 33 38 30 34 39 35 36 37
National, ISDN
918338049567
IE: 9 ( 2) : (7D) High layer compatilbility
91 81
IE: 10 ( 0) : (94) Lockshift codeset 4
IE: 11 ( 1) : (31) Transit counter
80
Counter: 0

 
That's odd. My first thought is someone has entered a * to delete something in AMO, and instead, they changed to *.

If you make a regen and search for * - which AMOs does it find?

It does look like a KNxxxx.

If you cha-diags, cp2, and set S05 on, you will get extra number modification diags in the hista, which helps sometimes. You could turn it on, make a test call, then turn off the diags (or hista gets flooded).

Full tracs trace would likely be more useful than the ISDN decode above.
 
Regen and tracs with diag flags does not offer any additional. thanks
 
Are you sure? Because regen and tracs trace is all I would expect to need to solve an issue like this from 4K perspective.

Tracs trace and diags output are two different things. Did you see the * appear on the number modification messages in hista?

What is the 4K software level?
 
The * is being inserted due to the KNDEF table
I changed the values of the field ISDNLC to ***** with ISDNSK set as 5.
The caller ID now shows *****713NXXXXXX on the outbound tandem call.
Set it back to ISDNLC * with ISDNSK set to 0.
Back to single asterisk.

If I could just figure out how to null these fields it would be fixed.
If you try a change with no field inputs it won't allow that.
The AMO guide alludes to changing the field to 10 asterisk symbols (default no local destination code).
It generates F12 error:
F12: ISDNLC CAN BE CHANGED ONLY TOGETHER WITH PARAMETER ISDNSK--so that does not work.
And the table cannot be deleted either:
F06: NNO 100 COULD NOT BE DELETED SINCE
A TOTAL OF 5816 SUBSCRIBERS OR ATTENDANT CONSOLES REFER TO
THIS VIRTUAL NODE (AMO SDAT RESP. AMO ACSU)

So this is quite the puzzle.
Any ideas?



DIS-KNDEF;
H500: AMO KNDEF STARTED
VIRTUAL NODE TABLE
+-----------+-------+--------------+--------------+-----------+-----+-----+----+
| VIRTUAL | TYPE | ISDN (E.164) | PRIVATE(PNP) | UNKNOWN |POPU-| CAC |DFLT|
| NODE | | CC | L2 | | LA- | PRE-| |
| NUMBER | | AC | L1 | |TION | FIX | |
| | | LC SK | L0 SK | NODECD SK | | | |
| | | UL | UL | | | | |
+===========+=======+==============+==============+===========+=====+=====+====+
| 100 |OWN | | | | 5816| | Y |
| | | | | | | | |
| | | * 0 | * 0 | | | | |
| | | EXT | EXT | | | | |
+ +=======+==============+==============+===========+=====+=====+====+
| | DPLN | ADPLN | |
+ +=======+==============+==============+===========+=====+=====+====+
+ | | |
+-----------+-------+--------------+--------------+-----------+-----+-----+----+
 



*****PROBLEM SOLVED*****

Took me a while to figure out how to eliminate the asterisk symbols
This command does it:

CHA-KNDEF:100,,,**********,0;
H500: AMO KNDEF STARTED
H06: PARAMETERS DPLN AND ADPLN HAVE NO EFFECT
AS THE VIRTUAL DIALING PLAN FEATURE IS NOT ACTIVE.
H02: NNO 100 CHANGED
AMO-KNDEF-111 VIRTUAL NODES
CHANGE COMPLETED;

Requires 10 asterisk symbols to configure the table to default with no destination code.
The 0 is the ISDNSK skip field.
I had tried doing this before and could not figure out the right command syntax.

Traces now show caller ID without the asterisk.

 
This is exactly what I mean when I said “
If you make a regen and search for * - which AMOs does it find?”

4K config does not by default have any *s in it. But that would have. Number mod diags should also have shown the number processing.
 
Moriendi--thank you. Hardest part was figuring out how to delete it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top