cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
374
Views
0
Helpful
1
Replies
dready
Beginner

CLID Wrongly Presented In The PSTN

We are running a VoIP network in two cities, area code 03 and 02 in Australia. We use SIP gateways. When an 03xxxxxxxx registered number makes a call to an 02xxxxxxxx number the call is routed ok and the correct originating CLID is present in the outgoing ISDN call setup.

The problem is, is that the "pilot" number of the 02 area code PRI is being presented to the called number instead of the correct 03xxxxxxxx

The 'show call history' shows all the correct info:-

CallerIDBlocked=False

OriginalCallingNumber=039012xxxx

OriginalCallingOctet=0x0

OriginalCalledNumber=029004xxxx

OriginalCalledOctet=0x0

OriginalRedirectCalledNumber=

OriginalRedirectCalledOctet=0x0

TranslatedCallingNumber=039012xxxx

TranslatedCallingOctet=0x0

TranslatedCalledNumber=029004xxxx

TranslatedCalledOctet=0x0

TranslatedRedirectCalledNumber=

TranslatedRedirectCalledOctet=0x0

GwReceivedCalledNumber=029004xxxx

GwReceivedCalledOctet3=0x0

GwOutpulsedCalledNumber=029004xxxx

GwOutpulsedCalledOctet3=0x0

GwReceivedCallingNumber=039012xxxx

GwReceivedCallingOctet3=0x0

GwReceivedCallingOctet3a=0x80

GwOutpulsedCallingNumber=039012xxxx

GwOutpulsedCallingOctet3=0x0

GwOutpulsedCallingOctet3a=0x80

and the 'dubug isdn q931' shows

Calling Party Number i = 0x0180, '039012xxxx'

Plan:ISDN, Type:Unknown

But 029016xxxx is always presented to the called party.

Is this our problem or is it the carrier's problem?

1 REPLY 1
dragos.stroescu
Beginner

Hello there,

From your description above it looks that the Call Setup is leaving your network with the correct CLID and Called No. (DNIS and ANI). If that is the case and the setup is entering into the PSTN with those correct values, but the call is presented at the destination with different ones (e.g. CLID) -> it is the PSTN problem.

Each PSTN CO has the ability to rewrite (partially or completly) the CLID to avoid "spoofing".

Probably there is a misconfiguration into the PSTN or the contract with the PSTN is imposing some "CLID's" on some specific ISDN trunks.

Normally when an enterprise is connecting to a PSTN via PRI the PSTN automatically rewrites the CLID regardless of the initial content.

Dragos