3Com Nbx 100 And Ss3 Nbx Administration Guide

							Receiving Calls451
Attendant ConsoleBy convention, NBX systems reserve extension 100 or 1000 for the 
Attendant Console (receptionist), although the Attendant Console can be 
assigned any internal extension number. Outside callers cannot reach 
internal extensions without operator involvement when incoming calls 
are directed to the Attendant Console. See “Adding an Auto Attendant”
 
in Chapter 6
.
Other ExtensionsIncoming H.323 calls can be routed directly to some other extension or to 
a phantom mailbox. Sales people often have phantom mailboxes because 
they are never in the office. Calls to their extension go directly to their 
voice mailbox. Note that phantom mailbox extensions cannot be used to 
forward calls.
Setting Up an H.323 Port Route
After you install an H.323 line port, you need to configure it. 
To configure a H.323 line port:
1In the NBX NetSet - Main Menu window, click Device Configuration.
2Click the Line Card Ports tab.
3Select an H.323 port. This port has the default setting from the Auto 
Discovery installation process.
4Click Modify.
5In the AutoExt field, enter the required extension number.
CAUTION:Do not route an H.323 port directly to another line port. 
Routing an H.323 call to a PSTN line, from the Internet, is dangerous 
because it would allow anyone to make long distance toll calls through 
the Call Processor — with no accountability.
6Click OK. 
						

							452APPENDIX A: CONNEXTIONS H.323 GATEWAY
Handling 
Conference CallsYou can include gateway port connections in local conference calls along 
with PSTN line connections. However, ConneXtions does not support 
conferences at the H.323 level, so, if two or more of the conferring 
parties are at a remote NBX system, each requires a separate port 
connection. This characteristic determines who can initiate the 
conference call.
A four-way conference call with three people at one NBX site and one 
person at the other site uses one H.323 port if it is set up from the side 
with three people. Otherwise, it needs three ports.
Related H.323 
DocumentationHere are some useful sources of information on the H.323 standard:
Web Sites
■http://www.packetizer.com/iptel/h323/
■http://www.itu.int/itudoc/itu-t/rec/h/
■http://www3.openh323.org/standards.html#where
Book
IP Telephony: Packet-Based Multimedia Communications Systems — 
Olivier Hersent, David Gurle, Jean-Pierre Petit (1999). 
						

							B
ISDN COMPLETION CAUSE CODES
This appendix lists the Completion Cause Codes displayed in the Span 
Status dialog box. The codes, listed in Table 80
, detail the reasons for the 
termination of a call. See “Configuring and Managing E1 
Digital Line Cards” in Chapter 3.
These completion cause codes descriptions are guidelines only. 
The detailed cause may vary according to PSTN.
Table 80   Completion Cause Codes
Class GroupingHex Code
Decimal 
Code
DescriptionDetails
Normal events0x000No diagnostic
0x011Unassigned 
numberThe requested destination, although valid, cannot be 
reached.
0x022No routeThe sending equipment (sending the cause) 
is requested to route the call through an unrecognized 
transit network. 
0x033No route to 
destinationThe called user cannot be reached because the 
network does not serve the destination.
0x066Channel 
unacceptableThe last identified channel is not acceptable to the 
sending entity.
0x077Call awardedThe incoming call is connected to a channel already 
established for similar calls (e.g. packet-mode X.25 
virtual calls).
0x1016Normal 
clearingThis call is being cleared by one of the users involved.
0x1117User busyThe called user cannot accept another call although 
compatibility is established.
0x1218No user 
respondingThe user does not respond to call establishment 
messages with either an alerting or connect indication 
within the allowed time.
0x1319User alerting 
no answerThe user has provided an alerting indication but no 
connect indication within the allowed time. 
						

							454APPENDIX B: ISDN COMPLETION CAUSE CODES
0x1521Call rejectedEquipment sending the cause does not wish to accept 
this call although it is not busy or incompatible.
0x1622Number 
changedThe called party number is not assigned.
0x1A26Non-selected 
user clearingThe user has not been awarded the incoming call.
0x1B27Destination out 
of orderThe destination interface is not operating correctly.
0x1C28Invalid number 
formatThe called party number is invalid, or incomplete.
0x1D29Facility rejectedThe network cannot provide the facility requested.
0x1E30Response to 
status enquiryThe reason for the STATUS message was the prior 
receipt of a STATUS ENQUIRY message.
0x1F31Unspecified 
causeUsed to report normal events only when no other 
cause in the normal class applies.
Resource 
unavailable0x2234No circuit 
availableAn appropriate circuit or channel is not currently 
available to handle the call.
0x2335Call queued 
(AT&T)The network is not functioning. Immediate redial is 
unlikely to be successful.
0x2638Network out of 
orderThe network is not functioning. Immediate redial is 
unlikely to be successful.
0x2941Temporary 
failureThe network is not functioning. Immediate redial is 
unlikely to be successful.
0x2A42Network 
congestionThe switching equipment generating this cause is 
experiencing a period of high traffic.
0x2B43Access info 
discardedThe network could not deliver access information to 
the remote user as requested. May include the type of 
discarded information (user-to-user information, low 
layer or high layer compatibility, or sub-address).
0x2C44Requested 
channel not 
availableReturned when the circuit (or channel) indicated by the 
requesting entity cannot be provided by the other side 
of the interface.
0x2D45Pre-empted
0x2F47Resources 
unavailable – 
unspecifiedReports a resource unavailable event only when no 
other cause in the resource unavailable class applies.
Table 80   Completion Cause Codes (continued)
Class GroupingHex CodeDecimal 
CodeDescriptionDetails 
						

							455
Service or option 
not available0x3149Quality of 
service 
unavailableThroughput or transit delay cannot be supported and 
that the Quality of Service (as defined in 
Recommendation X.213) cannot be provided.
0x3250Facility not 
subscribedThe requested supplementary service could not be 
provided by the network because the user has not 
completed the necessary administrative arrangements 
with its supporting networks.
0x3452Outgoing call 
barred
0x3654Incoming call 
barred
0x3957Bearer 
capability not 
authorizedThe user is trying to make unauthorized use of 
equipment providing a bearer capability.
0x3A58Bearer 
capability not 
availableThe user has requested a bearer capability, which is 
implemented by the equipment generating the cause, 
but is not available at this time.
0x3F63Service not 
availableReports a service (or option) not available event only 
when no other cause in the service (or option) not 
available class applies.
Service or option 
not implemented0x4165Capability not 
implementedThe equipment sending this cause does not support 
the requested bearer capability.
0x4266Chan not 
implementedThe equipment sending this cause does not support 
the requested channel type.
0x4569Facility not 
implementedThe equipment sending this cause does not support 
the requested supplementary service.
0x4670Only restricted 
digital availableOne equipment has requested an unrestricted bearer 
service but the equipment sending this cause only 
supports the restricted version.
0x4F79Service not 
implemented, 
unspecifiedReports the service (or option) not implemented event 
only when no other cause in the service (or option) not 
implemented class applies.
Invalid message0x5181Invalid call 
referenceThe equipment sending this cause has received a 
message with a call reference that is not currently in 
use on the user network interface.
0x5282Chan does not 
existThe equipment sending this cause has received a 
request to use a channel that is not activated on the 
interface for a call.
Table 80   Completion Cause Codes (continued)
Class GroupingHex CodeDecimal 
CodeDescriptionDetails 
						

							456APPENDIX B: ISDN COMPLETION CAUSE CODES
0x5383Suspended call 
exists, call 
identity does 
notA call resume has been attempted with a call identity 
that differs from that in use for any currently 
suspended calls.
0x5484Call identity in 
useThe network has received a call suspended request 
that contained a call identity (including the null call 
identity) that is already in use for a suspended call 
within the domain of interfaces over which this call 
may be resumed.
0x5585Incompatible 
destination
0x5888Incompatible 
destinationThe equipment sending this cause has received a 
request to establish a call that has low layer 
compatibility, high layer compatibility, or other 
compatibility attributes (for example, data rate) that 
cannot be handled.
0x5B91Transit network 
does not exist.
0x5F95Invalid message 
(unspecified)Reports an invalid message event only when no other 
cause in the invalid message call applies.
Protocol error0x6096Mandatory IE 
missingThe equipment sending this cause has received a 
message that is missing an information element that 
must be present in the message before that message 
can be processed.
0x6197Nonexistent 
messageThe equipment sending this cause has received a 
message with a message type that it does not 
recognize, either because it is an undefined message, 
or it is defined but not implemented by the equipment 
sending the cause.
0x6298Wrong 
messageThe equipment sending this cause has received a 
message that it considers as nonpermissible while in 
the call state; or a STATUS message was received 
indicating an incompatible call state.
0x6399Bad info 
elementThe equipment sending this cause has received a 
message that includes information elements not 
recognized because the information element identifier 
is not defined, or it is defined but not implemented by 
the equipment sending the cause. However, the 
information element is not required to be present in 
the message to enable the equipment sending the 
cause to process the message. 
Table 80   Completion Cause Codes (continued)
Class GroupingHex CodeDecimal 
CodeDescriptionDetails 
						

							457
0x64100Invalid element 
contentsThe equipment sending this cause has received an 
information element that it has implemented. 
However, the sending equipment was not able to 
implement the code because one or more of the fields 
were incorrectly coded.
 
0x65101Wrong 
message for 
stateThe received message is incompatible with the call 
state.
0x66102Timer expiryA timer has expired and an associated Q.931 error 
handling procedure has been initiated.
0x67103Mandatory IE 
length error
0x6F111Protocol errorreports an error event only when no cause in the 
protocol error class applies.
Interworking0x7F127Interworking 
unspecifiedThere has been interworking with a network that does 
not provide cause codes for its actions. Therefore, the 
precise cause for a message being sent is not known.
Table 80   Completion Cause Codes (continued)
Class GroupingHex CodeDecimal 
CodeDescriptionDetails 
						

							458APPENDIX B: ISDN COMPLETION CAUSE CODES 
						

							C
CONFIGURING OPTION 184 ON A 
W
INDOWS 2000 DHCP SERVER
OverviewWhen you configure option 184 on a Windows 2000 DHCP server, you 
enable the server to pass the IP address of the NBX Call Processor to NBX 
devices such as telephones.
This appendix provides information on how to configure option 184 on 
an existing Windows 2000 server system that has been configured to run 
the DHCP server software.
Assumptions
■The information in this appendix pertains only to a Windows 2000 
server. The configuration instructions differ for other DHCP servers.
■This appendix describes only the configuration of option 184, not the 
installation of the Windows 2000 server or the configuration of the 
DHCP server software. 
Configuring 
Option 184To configure option 184 on a Windows 2000 DHCP server, you:
■Create the new option
■Edit the option
■Activate the option
Creating Option 184
1Start the DHCP Microsoft Management Console:
Start > Programs > Administrative Tools > DHCP
The DHCP dialog box appears. In the left pane, look for the name of your 
Windows 2000 DHCP server.
2Right click on the name of your DHCP server. From the menu that 
appears, select Set Predefined Options. The Predefined Options and 
Va lu e s dialog box appears. 
						

							460APPENDIX C: CONFIGURING OPTION 184 ON A WINDOWS 2000 DHCP SERVER
3Click Add. The Option Type dialog box appears.
4In the Name field, type a name of your choice. For example, because you 
are configuring this option to work with the NBX system, you might 
choose NBX as the name.
5From the Data Type pull-down list, select Byte.
6Enable the Array check box.
7In the Code text box, type 184.
8In the Description text box, enter a description of your choice. Example: 
NBX NCP IP Address.
9Click OK.
In the Predefined Options and Values dialog box, the DHCP Microsoft 
Management Console creates a new option name by combining the 
option number with the name that you chose and adds this name to the 
Option name pull-down list. Example: If you used NBX as the option 
name, the system adds 184 NBX to the pull-down list.
Editing Option 184
Va lue s
1Select the new option name from the Option name pull-down list, and 
click Edit Array. The Numeric Value Array Editor dialog box appears.
2In the Data entry area of the dialog box, click the Decimal radio button at 
the right of the word Format.
3In the Current Values text box, highlight the 0 (zero), and click Remove.
4To create the new value, enter each element of the new value:
aClick in the New value text box.
bType the individual element value.
cClick Add.
5Repeat steps 4 a, b, and c for each element. As you add each element, it 
appears in the Current values list, above previously added values.
Add these elements in this order:
What you typeDescription
1Enter 1 as the only suboption code for option 184. (Some 
options can have more than one suboption.)