cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Get the latest new and information the November issue of the Cisco Small Business Monthly Newsletter

SPA9000 Inbound Call Routing

5332
Views
0
Helpful
2
Comments

Two inbound scenarios can exist in a SPA9000 environment.

i. Calls come in via a SIP trunk that the SPA9000 is registered to

ii. Calls come in via a PSTN trunk on a SPA400 that the SPA9000 is registered to

An office may have some general DIDs and some private DIDs.

General DIDs should ring the AA or a configured hunt group while private DIDs should ring the desk of the owner of the private DID.

Configure Inbound Call Routing as Follows:

  1. Identify the called number to be routed and document it, example 3335551212
  2. Identify the target of the called number, example extension 35
  3. Identify the Line tab of the SPA9000 that is registered to the SIP trunk/SPA400 3
  4. SPA400: Identify the port that the line carrying 3335551212 is attached to, example 2

    SIP trunk DID Inbound Call Routing:

    1. Use the SPA9000's web-ui to change Voice tab > Line N tab > Contact List: 3335551212:35| [original contact list info]
    2. Scroll down and click Submit All Changes

    PSTN trunk DID Inbound Call Routing:

    1. Use the SPA400's web-ui to change Setup tab > Basic Setup > Port ID > Port ID 2: 3335551212
      [You replace FXO_Port_ID_2 with the DID associated with the port]
    2. Scroll down and click Save Settings
    3. Use the SPA9000's web-ui to change Voice tab > Line 3 tab > Contact List: 3335551212:35| [original contact list info]
    4. Scroll down and click Submit All Changes

Enjoy.

<end>

Comments

How do I configure a line as a true "shared" line that is like a Party line where all employees (5 of us) can pick up and participate in like a conference call or party line whether it is an external call or internal call?

Beginner

Just a note; I came across a situation recently where the spa9000 simply would not recognize the DIDs in the Contact List field under Line 1 (wherein Line 1 registered the spa400). This was with the newest firmwares on both spa9000 (6.1.5) and spa400 (1.1.2.2). However, it did work when mapping the FXO_Port_ID_1 to the extension, not by renaming the port ID to the DID and usign the DID in line 1. I'm unsure if that was an isolated issue but it's worth mentioning.

Example:

Contact List: FXO_Port_ID_1:101,cfwd=aa|FXO_Port_ID_2:102;cfwd=aa|

In that instance I left the FXO port ID's default on the 400

Instead of: 2125551234:101,cfwd=aa|2125555678:102,cfwd=aa|

In that instance I had changed the FXO port ID's to the applicable DID's. This would not work.

As always, Patrick, great docs, they have been an instrumental help to us!