HiPath 4000 v4 A-number presentation restricted

[HIREI]

Hi, all!

Please, how to set "presentation restricted" on analog or digital port? For example, we have ext. number (local port) 3543, and for external calls through PRI EDSS1 we should have in SETUP message Calling Party Number (CgPN)=3543 and CgPN Presentation Ind.=Restricted not Allowed. What are the commands? Thanks in advance!

Excuse me, I'm not a HiPath specialist.

 

[Iamnothere]

Perhaps someone else will immediately know how to help, but I would need further info. Are you trying to send the calling party number, or block the calling party number from being sent? Or replace the actual calling party number with a generic number? For specific stations only, or the entire system? Please explain in detail what you need to accomplish.

 

[HIREI]

Thanks for the replay!

I'm trying to send the calling party number, for example, 3543, to the AXE-10 exchange and 'say' this exchange that the number presentation is restricted.

In other words, SETUP message must include:

Calling party number=3543
Presentation indicator=Restricted

For specific station (local port) only.

_________             __________
|       |             |        |       ________
|       | PRI EDSS1   |        |       |      |
| AXE   |<----------->| HiPath |-------| 3543 |
|       | CgPN=3543   |        |       |      |
|       | Pres.Ind.=  |        |       |Subscriber 
|       | Restricted  |        |       --------
---------             ----------

 

[HIREI]

Now we have all the same but Presentation Ind. = Allowed. So, the question how to change Allowed to Restricted.

 

[Iamnothere]

That's a European ISDN protocol, for which I have zero experience. If you have no HiPath 4000 experience, finding the culprit parameter may be very challenging. I suggest that you download the HiPath 4000 V5 AMO reference manual from a recent thread in this forum. I can offer a few suggestions of where to look in the 4K:

AMO LDAT: parameter "LATTR" (in English) - controls what is actually sent across a particular trunk group during specific calls. Attributes can be daisy-chained in this field. Look at "PUBNUM", which indicates that the Public telephone number should be sent for each call on this particular route/trunk group, and "SUPPRCPN" (Suppress Calling Party Number).

AMO TDCSU: the AMO that is used to define your ISDN circuit. The device type, protocol, trunk group, B-channels, etc, are specified here.

AMO LWPAR: contains more trunk/connectivity settings.

These are merely suggestions. I hope a euro-trunk specialist can help. Good luck!

 

[HIREI]

Thanks! We discussed "SUPPRCPN" (Suppress Calling Party Number) but we think that in this case AXE-10 will receive no CgPN.

I've downloaded v5 manual and find this:

PRESCAL Presentation of calling line number
Type of Input : single value, 4. parameter of a min-1-group (CHANGE) single value, optional (ADD,TYPE=SCRDATA)
Possible Values :
<...>
CLIRPERM = restriction of permanent A-subscriber, no presentation.

May be it's the solution?

 

[HIREI]

In MML language we could put something like this:

XXXXC:EXTNUM=3543, PRESCAL=CLIRPERM;

But, of course, this is not a HiPath case.

 

[donb01]

I'm going to ask the obvious question: Is there some specific reason you need the CPI info completely blocked??

At my organization in the U.S. I was blocking CPI using the phone menu, which then blocks everything going out and makes it say "Private" in caller-id, but then found out that some of the carriers now offer a service called Privacy Manager that blocks calls from numbers that have their CPI restricted, and that causes a hassle for our staff.

So for this reason, rather than blocking the information I change the information on the BASIC3 tab to present the main published number of the building they are calling from. In the case of our medical profession this keeps the patients from getting the private numbers of the Doctors and Nurses that are calling them and instead gives them the front desk number for that clinic.

This is easy to do, especially on a PRI, so it might be a consideration for you?

 

[Iamnothere]

That could very well be it, but as I said, I have no experience with EDSS1 protocol. The AMO to which you are referring is AMO SCREN, which I have never used, and have never SEEN used anywhere, but the documentation does indicate that it is used in conjunction with EDSS1. Therefore I have no suggestions, but I have attached some "AMO SCREN" info.

Please post if/when you resolve the problem!

 

[HIREI]

Thank you all!!!

"using the phone menu" and "on the BASIC3 tab to present the main published number" sounds reasonably. Thanks for pdf.

The matter is that some mobile operators in Russia displays Generic number in ISUP IAM message instead of Calling Party Number.

We at AXE-10 suppress (deleted) the Generic number by the Screening mask. Some other clients become angry )) . Now I have a directive from Boss to give up the problem because displaying Generic number is not legal...

And those who have HiPath are our client...