Dhcp option 160 cisco ip phones
Techniques are provided for sending from a client in a network device a request message configured to request configuration parameters to allow the network device to operate as a source or destination node for packet switched network telephony activity. In response to receiving the request message, sending the configuration parameters from a server configured to retrieve the configuration parameters from a call provisioning server.
The configuration parameters are received at the client and passed to a call agent in the network device in order to configure the network device to operate as a source or destination node for packet switched network telephony activity. The present disclosure relates to network provisioning and more particularly to provisioning a device for voice over a packet switched network. VoIP is also referred to as Internet telephony, broadband telephony, or voice over broadband.
To ensure real-time delivery of voice and video the packet data may be further encapsulated in a protocol that can provide a quality of service, e. As with traditional PSTN services, phone calls must be set up when a number is dialed and torn down when a user hangs up the phone. Before signaling can begin, however, the VoIP phone or terminal involved in the call needs to be provisioned. Referring first to FIG. The system comprises a network device and a server device Between the network device and the server device is a network to allow the two devices to communicate.
The network device comprises a data processing devicean interface unitand a memory The server device comprises a data processing devicean interface unitand a memory The SCA provisioning process logic S is configured to provide call provisioning information or parameters.
It is to be appreciated that the DHCP client and the CCA shown in connection with network deviceand the DHCP server and Call provisioning server shown in connection with server device may be software modules that may be instantiated in several devices and they need not reside together in any one device, respectively. Furthermore, the client process logic C may be implemented in a software module that is part of the DHCP client and the server process logic S may be implemented in a software module that is part of the DHCP server Instead of DHCP other protocols may be used, e.
The data processing devices and may be microprocessors, microcontrollers, systems on a chip SOCsor other fixed or programmable logic. The memories and may be any form of random access memory RAM or other data storage block that stores data used for the techniques described herein.
The memoriesmay be separate or part of the processors, respectively. Instructions for performing the client process logic C may be stored in the memory for execution by the processor and instructions for performing the server process logic S may be stored in the memory for execution by the processor The server process logic S retrieves the provisioning information requested by the client process logic Cand sends the provisioning information back to the network device The interface units and enable communication between the network device and the server deviceand ultimately to other network elements including the clients, agents, and servers in the system The functions of the processors and may be implemented by logic encoded in one or more tangible media e.
Thus, the client process logic C and the server process logic S may be implemented with fixed logic or programmable logic e. The network device and server device may interface to a call manager as part of a call management system. Such a call manager is described hereinafter in conjunction with FIG. The network device and server device may be a general purpose computer e.
Alternatively, the network device may be a SIP-enabled phone or SIP phone, or other packet switched telephony enabled terminal, such as an H. The network device and the server device may run custom, proprietary, or commercial off-the-shelf applications that may be configured to implement the client process logic C and server process logic Srespectively.
Also as part of the power up process, CCA starts up and client process logic C becomes active. Listing 1 shows options and within the option 55 parameter request list using plain text format. The server process logic S retrieves the requested configuration parameters and indicates to the DHCP server to respond with a DHCP acknowledgement ACK message that contains the requested configuration parameters.
The server process logic S has returned the SIP server IP address under option and a number of user selectable or user configurable parameters under option The types of user configurable parameters may also be set using a factory default or tied to a particular enterprise ID described below. In one example, the phone number could be used for outside or inter-office communication and the additional phone number could be a local extension for an IP private branch exchange IP-PBX phone system used for intra-office communication, or vice versa.
Listing 1 and Listing 2 are formatted in plain text for readability. In actuality, the messages are sent as hexadecimal numbers according to a specific format.
The fields in the message could be easily adapted, e. For example, Listing 2 has a placeholder for a Gatekeeper IP address option which may be used for H. Continuing with reference to FIG. The client process logic C extracts the provisioning information or configuration parameters and passes the configuration parameters to the CCA The CCA then provisions itself using the configuration parameters with no manual or user intervention required.
In an alternate example the client process logic C provisions the CCA directly, again without manual or user intervention. Once provisioned the CCA registers the phone numbers with the Call provisioning server via a network device register message e.
If registration is successful, the Call provisioning server acknowledges the network device register message e. The network device is then operable to dial originate callsanswer calls, or hang up terminate calls using the CCA Turning now to FIG. Network comprises a plurality of network devices 1 - N that are similar to network device of FIG.
This information may be collected during periods of low network utilization, i. The call manager may contain analogous or similar elements, components, or modules as network devicesuch as a data processing device, an interface unit, and a memory, each of which are not shown.
The call manager may also contain a DHCP relay, e. However, unlike the systemcall manager cannot directly provision CCA As depicted in FIG. In another example the client provisioning process logic or a DHCP relay resident within the call manager is configured to automatically provision CCA directly without manual intervention.
If a user of network device calls remote network device then CCA sends a call invite message to remote network device via CCA and Call provisioning server At that point in time the phone call is set up and communications may commence between network device and remote network device as indicated by the dashed line in FIG.
Reprovisioning may be necessary, for example, when network topology has changed, if traffic load needs to be balanced across network devices and servers, when devices are upgraded, and for time-of-day traffic rerouting. The DHCP server responds with the new provisioning information, e. Referring now to FIG. Client process logic C logic comprises blocks CCand C that are executed by the network device Server process logic S logic comprises blocks S and S that are executed by the server device At Ca request message is sent from a client in a network device configured to request configuration parameters to allow the network device to operate as a source or destination node for packet switched network telephony activity.
At S the request message is received by a server. In one example, the request message is a DHCP request message requesting vendor-specific information. In one example, option is placed under DHCP option 55 and requests the vendor-specific information. A SIP server address may also be requested under option The vendor-specific information may be any information needed to provision the call agent for packet switched telephony using any suitable signaling protocol corresponding to the capabilities of the network device.
At Safter receiving the request message the server responds by sending configuration parameters retrieved from a call provisioning server that allows the network device to operate as a source or destination node for packet switched network telephony activity. The server process logic S is also configured to return a specific user configurable set of vendor-specific parameters when option is received in the DHCP request message. At Cthe configuration parameters are received at the client in the network device, and at Cthe configuration parameters are passed to a call agent in the network device using, e.
The call agent, e. Embodiments described herein provide dynamic plug and play provisioning for telephony enabled network elements with no manual user intervention. These techniques are useful for household consumers, enterprise users, and service providers while maintaining standard network security methods. In this way, even a large network with several hundreds or thousands of devices can be easily managed with reduced down time and with reduced help desk resources.
Although some embodiments are described herein with respect to SIP networks and devices, the methods are easily extensible to any general VoIP deployment for any configuration including any number of endpoints, gateways, servers, IP-PBXs, or back to back user agents. Other signaling protocols may be used, e.
The signaling protocols may be used in conjunction with other protocols or standards for signaling and transport, e. Authentication and accounting protocols may also be employed. The configuration parameters are passed to a SIP user agent in the network device in order to configure the network device to operate as a source or destination node for network activity.
Although the apparatus, logic, and method are illustrated and described herein as embodied in one or more specific examples, it is nevertheless not intended to be limited to the details shown, since various modifications and structural changes may be made therein without departing from the scope of the apparatus, logic, and method and within the scope and range of equivalents of the claims. Accordingly, it is appropriate that the appended claims be construed broadly and in a manner consistent with the scope of the apparatus, logic, and method, as set forth in the following claims.
The method of claim 1wherein sending the configuration parameters comprises sending configuration parameters for a signaling protocol that allows the call agent to set up and terminate a packet switched network phone call.
The method of claim 1wherein sending the request message comprises sending a dynamic host configuration protocol DHCP request message configured to request vendor-specific information in order to provision the call agent for a corresponding signaling protocol.
The method of claim 4wherein receiving the configuration parameters comprises receiving session initiation protocol SIP user agent provisioning information, and further comprising provisioning the call agent using the SIP user agent provisioning information. The method of claim 5further comprising: The method of claim 1further comprising: The method of claim 1wherein sending the request message comprises sending the request message from a call management device, receiving comprises receiving the configuration parameters at the call management device, and further comprising provisioning the call agent via the call management device.
The apparatus of claim 9wherein the memory further stores instructions that, when executed, cause the processor to set up and terminate a packet switched network phone call using a signaling protocol via the call agent.
The apparatus of claim 9wherein the memory further stores instructions that, when executed, cause the processor to send a dynamic host configuration protocol DHCP request message that is configured to request vendor-specific information in order to provision the call agent for a corresponding signaling protocol.
The apparatus of claim 12wherein the memory further stores instructions that, when executed, cause the processor to receive the configuration parameters comprising session initiation protocol SIP user agent provisioning information, and to provision the call agent using the SIP server address and SIP user agent provisioning information.
The apparatus of claim 13wherein the memory further stores instructions that, when executed, cause the processor to: A system comprising the apparatus of claim 9and further comprising a dynamic host configuration protocol DHCP relay configured to: A system comprising the apparatus of claim 9and further comprising a call management device coupled between the server and the apparatus, wherein the call management device is configured to: Logic encoded in one or more tangible media for execution and when executed operable to: The logic of claim 17wherein the logic that sends comprises logic configured to send the request message configured to request vendor-specific information, and the logic that receives comprises logic configured to receive vendor-specific information comprising call agent provisioning information, and further logic configured to provision the call agent using the vendor-specific information.
US USB2 en Supporting simple IP with address translation in a wireless communication device. Communications device, router, communications system, and control method for communications device and router.
Hi dhcp option 160 cisco ip phones, I have a problem were my polycom phones are randomly rebooting and freezing in 2 different offices.
This is my provisioning process: This is the App log from a that just rebooted: Current logging level 4 Using Base Profile Generic Primary DNS server is not specified Alternate DNS server is not specified Zero servers configured Value for configuration parameter dir. Value 0 for configuration parameter reg. Could not copy key to new slot Could not copy cert to new slot Could not copy SIP user to new slot Could not copy SIP uuid to new slot Could not copy server to new slot Instruction 1 chord 0 of sound effect Message waiting not found Instruction 2 chord 0 of sound effect Message waiting not found Instruction 3 chord 0 of sound effect Message waiting not found Current logging level 3 app1 03 Initial log entry.
Current logging level 4 app1 4 03 Default StatusBar is disabled app1 4 03 mb. Current logging level 4 app1 03 AppPhoneC:: Current logging level 4 ldap 4 03 cDynamicData:: Failed efk 03 Initial log entry.
Current logging level 4 utilm 4 03 uBLFCompressed: Ready for Call, uptime: The only difference is that one office is running pbx 12 and the other Also, I am not using any vlans in the phone network, so all phones and the phone server are in the same VLAN. Thank you for your responses.
Dhcp option 160 cisco ip phones are the settings in the template: T xxxxxxxxx xxxxxxxxx xxxT Firmware Version: Firmware Slot 1 Provision Server Address: I have complete control over the pool which is Dhcp option 160 cisco ip phones you help me understand why do you think the IPs could be causing the problem?
This particular phone mine just happened to receive the very first IP of the pool You need to make sure that there are no static addresses anywhere in your range.
Your system managed to assign the address What is likely to happen is that any traffic for any server, phone, or printer in the network is going to get responded to by one of your phones. Thank you for the responses, in this network there are only polycom phones and 1 phone server, nothing else, the IP range can be easily modified. But in this particular dhcp option 160 cisco ip phones the issue is not the IPs or the range, but the fact that the phones reboot randomly, the phones reboot even when they have static IPs entered directly in the phone.
Try putting a known good POE switch in place of the existing switch even on the floor to test and see if the runtime is different. Your FTP server logs may help confirm or deny this issue. Alternately attach a local power brick to a dhcp option 160 cisco ip phones test phones and see if they go out ; if not, dig into the UPS. Polycom phones rebooting and freezing General Help. This is my setup: This is my DHCP config file: Yes that is correct.
Again thank you for looking into it. Your DHCP server has been instructed to hand out dynamic addresses in this range.