You can use the above method to very quickly track down errors in your call menu.
Click the button within the banner to force a configuration file push from Fonality's Data Center to your {{ fon.product( site.hostname ) }.
Most customers experiencing a call routing issue find that they made changes to their internal structure but forgot to update the PBXtra .
Premise-hosted PBXes only.
Analog telephone lines (POTS, or Plain Old Telephone Service) don't tell the PBX what number the outside caller dialed to reach the PBX. Analog lines just ring. Therefore, inbound call routing by number dialed on analog lines has to be done based on the physical port the telephone line is connected to.
To clarify:
Let's say the PBX has four analog telephone lines connected to it. To test, call the number that needs to be routed specially. On the Web Admin Panel, go to Status -> trunks. It should show which analog port is in use. Mouse over the double arrow "»" to see which channel it's using. Note this down.
Then go to AutoAnswer -> edit call menu, and change the "Go to submenu by number dialed" sequence to the appropriate card and port. See the example on the right -->
Use a similar approach for DID-to-extension routing (numbers that ring someone's extension directly), under the extension settings. See the example on the right -->
For more information, please see: