Depends on the name you want it to show, there are settings for the station name to be sent to other Avaya Systems via ISDN but if you want a general name to be displayed on all outbound calls that would be done through your telco.
To send the station name when ISDN to ISDN connection is made between Avaya systems you would set Send Name to yes in the Trunk Group form.
Agreed, but many of the calls are not ISDN to ISDN. These are calls to home etc. If the person being called has privacy manager, not accepting no-name calls, the call does not go through, even though the telephone number is being sent. Software in system is too old to do a list trace tac, so this can not be used.
As justinsm2 suggests, I'd start with the Telco. The real question I'd ask is whether a valid number is being sent with the calls? Is it always the same number? If so, have the Telco check the LIDB database name for that number. It could be set to "unknown name". It could also be set to private number, which the Telco can control. If a number is not showing up, then you either need to send a 10 digit DN, or the Telco needs to put in a default number if you don't send it.
As for sending your own name from the PBX, I've run into problems with some terminating CO's rejecting calls where the name is sent from the PBX rather than from a LIDB lookup.
The telephone number is sent and can be changed using the isdn pub/unknown screen. The main problem is the president can't call home as he has privacy manager from LEC. Call comes up with telephone number, but no name, on other local employee's home telephones, one employee says his caller id shows "unknown name" on his caller id box at home.
Yes, I have the same problem. The PRI is insisting they are sending it and have Send Name stroked to Y in the trunk group. Actually, I have never seen a name accross our PRI on inbound cals.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.