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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

outgoing CLI

Status
Not open for further replies.

Thermus

Programmer
Jul 3, 2003
176
NZ
Hi

I have an IP500 running ver 4.1.12 with some minor issues outputting CLI.

The Telco here is able to provide extn level billing, where the IPO forwards the callers extn number down the ISDN, and the Telco picks up the number and provides a statement for each extn.

The issue I have is when a call comes into a hunt group via ISDN, gets an extn that is universal call forwarded to an external number and goes out again via ISDN. The call connects fine and all is good except the CLI sent to line is empty in the calling party field.

The monitor trace of ISDN layer 3 confirms this and further down the trace of the call the hunt group number is displayed, but not in any useful manner for the telco to use it.

Does anyone know of a way to force the calling party extn number out the ISDN?

Current set up is:

?,.sE,0,Dial


 
DDI comes into sequential hunt group. there is one extn in the hunt group universally forwarded to a short code.
The short code dials the external number.

If the DDI is directed to the extn, correct CLI is sent out.

DDI is directed to Hunt group, incorrect CLI sent forward, Call still connects.
 
I had it, it happens on all outgoing calls as well.
It is due to the fact the IPO decides not showing the user CLI if the user belongs to a HG.
The only solution I found is providing specific user short codes.
 
Your in the UK I'm guessing, is this on PRI or BRI?

Have you tried not forwaring the user to a shortcode but to the number itself? Haven't had to deal with something like this.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top