It includes an in-depth analysis of the concept and contains diagrams to help the learning process. To help get the picture, here is an example of a typical network that contains a Cisco CME router connected to the Internet and pstn network, along with a Cisco voice-capable switch it is able to identify voice packets with a couple of workstations and IP phones.
The concept is pretty straightforward, however, pay attention to how the Cisco CME router connects to the local network and how some IP phones connect to the network and workstations behind them.
Due to the fact IP phones occupy a network port to connect to the local area network, Cisco has equipped most IP phones with a switch allowing a workstation to connect directly to the IP phone. This method obviously has the advantage of cutting in half the required switchports for IP phones and workstations.
In this scenario, the link from the switch to the IP phone is configured as a ' Trunk ' link where as the link between the IP phone and workstation is configured as an ' Access ' link. The general idea is that we use trunk links to the IP phone and from there an access link is provided for the network device, usually a workstation.
If there is only one device connecting through one port, then this can also be configured as an access link assigned to the VLAN required. The type of connection used will be dependent on the density of connections needed, technology available in the region, cost of the connections and the interfaces present on the router.
The example below shows a Cisco router populated with 4 interfaces. Each interface is inserted into one of the available four slots and, once the router is powered up, if the IOS supports the interface installed it will automatically recognise it and provide the engineer access to the appropriate CLI commands so it can be configured.
At this point, it is important to mention that there are over 90 different interface cards that can be used on Cisco routers. The two main types of interfaces are the Data interfaces and Voice interfaces. Below is serial data interface card normaly used to terminate leased lines connecting remote company offices with their headquaters:. Leave a Reply Cancel reply Your email address will not be published. This website uses cookies to improve your experience.
We'll assume you're ok with this, but you can opt-out if you wish. Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website.
Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website.
These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary Necessary. Necessary cookies are absolutely essential for the website to function properly. At first, you need to configure the voice service Figure 3. The most important values for the configuration are the IP address of the service and the maximum number of registrations on your system. The service IP address must be your router's IP address. The standard port number for the SIP service is Figure 4 - Global SIP configuration. The number of this SIP endpoint will be , and it will use the G codec.
By following the pattern above you can add as many SIP accounts you want. If you have set up everything properly, you can start registering your SIP endpoints to Cisco Call Manager Express by using the account data you added to it. After you have your endpoints registered properly, you can use the system with all of the features provided by Ozeki VoIP SIP SDK like holding calls, blind transfer, attended transfer etc.
Figure 7 - Making a call between number and If you have any questions, do not hesitate to contact us at: info voip-sip-sdk. Net developers.
0コメント