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!

Networking problem OS4k v7 and v10 (how to hiding names and CF infos)

Status
Not open for further replies.

jarmac

Technical User
Oct 2, 2012
58
PL
Hello

I have two networked system V7 and V10 via PRI ISDN
Q:
1.How to do not send subscribers names via net ECMAv2 protocol. - is there a way?.

2. Is it possible to turn off the transmission of information about Call Forwarding in the network?
(if someone has activate CF then remote system try to make forward via own lines - (i don't wont this) is it like path optimization or something ?

regards
jarmac
 
What is wrong with names and forwarding information ?
The main idea of networking system is to have them transparent to end users.
 
Hello sbcsu

Of course, there is nothing wrong with the normal operation of the systems when cross-linking.

These are the two clients who are "lucky" to be OS4K owners. one wishes the names of the subscribers not to be sent to the other, a simple request.
I can not set the number to be hidden because it also works for internal calls.

The only thing I managed to do was to set it to connect to the EDSS1 protocol, but it did not work correctly at the time of CF setup, as I wrote in the question no.2

So maybe you have any idea how to disable names in normal Cornet-NQ networking and disable CF element in ISDN setup in case of call forwarding

greetings
jarmac
 
If the 2 sites are different companies then they do not need to contact one another ?

Change the protocol of the trunks between the 2 systems.
Try COP/COT parameters - NONA I think from memory is one (send no name)
If you use a non-intellegent protocol like a central office protocol between the systems
then they may not transfer the information that you want stopped.
 
Ad.2
The COT of the mentioned PRI line should not included FNAN and FWDN parameters.
 
Hello

Thanks, I will try do some changes next week, we will see

I have found more nice looking param in COT
for example:
BKNA Activation disables feature Calling Name Delivery
RMVN Remove name

but what they do, that is a question

regards
jarmac
 
They do what they say !
Make a new COT/COP (Copy the originals)
Change the Trunks to that new COP/COT -
(CHA-TDCSU:pEN=1-1-1-1,COTNO=XX,COPNO=XX,COTX=XX;)
Experiement then using the parameters - Don't worry - you won't break anything

To change it back just change the trunk back to original COP/COT
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top