Sometimes, the same UC500 and IP phone user site may serve different companies. It is therefore important, to be able to identify the inbound call based on the called number. There are several ways to do this:
1) Configure directory entries (under telephony service) for the DIDs and associate the entries with appropriate company name. In addition to this, the "service dnis dir-lookup" needs to be enabled under the telephony-service. Please note that this command is enabled in the default configuration files for UC500, so the only thing that is needed, is create directory entries.
2) Have each inbound number ring on different line buttons of the IP phone. This would give a quick visual indication of which company is being called, and each button can also be labeled with the appropriate company name. The idea is the to segregate the dialplan. See below:
- Create new Class of Restriction lists:
! dial-peer cor custom name IncomingRuleA name IncomingRuleB ! dial-peer cor list CompanyA member IncomingRuleA ! dial-peer cor list CompanyB member IncomingRuleB
The idea is to segregate the dialplan. An incoming call on one of the FXO ports will trigger a connection plar to an octo dn that is part of that CORLIST ONLY. That octo DN will be shared by all phones in that group. If there is phone overlap (one phone belongs to more than one group) then you can map the octo DN to a different button on the same IP phone. That way, the user can visually differentiate calls between company A and company B.
Notice that the global commands to define the corlist members are not included here (previous example had instructions on how to add them).
Also, you may have many more POTS dial peers because of your dialplan. You will need to group them accordingly and map a corlist to each group.
Hello,I am configuring a RV160 as OpenVPN server. And I've got two problems:After configuring the router I try to make a connection from "OpenVPN Connect" (as I have done to other OpenVPN servers).I can't connect and I get the error "EVENT: option_error: ...
Hi all, We have an odd problem and wondering if anyone else has experienced the same problem and found a solution. We have tested connecting our CP-7841 IP phone on two different networks that work fine with any other device, but the phone is t...
I have a customer in Berkeley, CA that just got the Sonic.net Gigabit Fiber installed. They currently have a RV180W as their wireless router. I don't think it is up to the task. I am planning on replacing it. Before I do what router...