Home » Forums » Vendor Forums - Non-Certified » Linksys/Cisco

Trixbox & SPA-8800 Interfacing

SovComm
Posts: 2
 Member Since:
2011-12-05
Submitted by SovComm on Mon, 12/05/2011 - 8:16pm.

Trixbox CE, Cisco SPA-8800 VoIP Gateway
Netgear 24PoE Switch, CISCO VLAN Router (192.168.10.xxx)
x10 Grandstream GXP-2000 (SIP Devices)
-----------------------------------------------------------------------------------------------------------------------

We are Resellers for Digimerge & 3CX and have Installed 3 other 3CX Systems with no problems with Grandstream VoIP Gateways. Seemlessly. This is our first installation with Asterisk/Trixbox CE & of this Magnatude. Our Previous Installs are for Small Businesses with x2 VoIP Trunks & Non Specific Dialing. Auto-Configs were used.

QUESTION: Attempting to interface the SPA8800 with Trixbox (Most Recent Ver.) & 10 GXP Phones.
Situation: 4 Business that have merged together and we are configuring an SPA-8000 to bring in all 4POTS to VOIP for this client.
What I am looking for is an example of someone who has completed the same effort, and could give me a configuration example?

4 Lines, 4 Seperate Businesses, 10 GXP's Monitoring all 4 Lines, Dialing out specific SLA's.
Line 1 (SLA1) - Business 1 - IVR 1
Line 2 (SLA2) - Business 2 - IVR 2
Line 3 (SLA3) - Business 3 - IVR 3
Line 4 (SLA4) - Business 4 - IVR 4

Now, the IVR and Ring groups I have down pat. I just am having an Incoming and Outgoing Dialing issue per FXO port. I keep getting an "ALL CIRCUITS ARE BUSY" when attempting to dial out. Is anyone out there with a similar configuration?

Also, If you have GXP's with Softkeys as SLA's, Could you please post your config's for me to reference to? We want all phones to monitor all 4 Lines. Thanks!

______________________________________________________
Voice/Data/Wireless/Multimedia Solutions
"We play outside the box!"
www.sovcomm.ca | (902) 789-9725
Jordon Fenton (President & Technician)

Thanks from the gang @ Sovereign Communications!

‹ Cisco 7975 won't register to trixbox? Dialing *280 transforms into *28 ›


SkykingOH
Posts: 9678
 Member Since:
2007-12-17
Three things: 1 - Why would
Mon, 12/05/2011 - 9:33pm

Three things:

1 - Why would you use an unsupported out of date distro on a new install?

2 - You did not post your trunk and Grandstream config so how can anyone give you any suggestions.

3 - SLA is not supported in any version of Asterisk/FreePBX - SLA can be configured manually via SLA.conf with DAHDI hardware. It is not supported via the FreePBX GUI.

--

Scott

aka "Skyking"



SovComm
Posts: 2
 Member Since:
2011-12-05
Im sorry, but that was kind
Mon, 12/05/2011 - 10:59pm

Im sorry, but that was kind of un called for>

1 - Why would I use an outdated install? Where in my post was there any reference to an outdated distro? States it is most recent.
2 - Im back home at the office, so no access to current config snapshots (No ISP @ Host Location for Remote)
3 - SLA IS Supported with the devices using the softkeys instead of Line 1, Line 2, Line 3, Line 4 - Of coarse it is not done on the ASTERISK GUI. Which is why I was looking for snippets I could reference from.

Here is the config for each trunk changing the name and secret from line1, line2, line3, line4 for each FXO port.

SPA = 192.168.10.53 (Static Assigned)
Trixbox = 192.168.10.51 (Static Assigned)
GXP's = 192.168.10.210 - 219 (Range 210-219 Each Static Assigned)

SIP Trixbox Trunk GUI Menu:

SIP\line1
Trunk Name:line1
PEER Details:
type=friend
secret=line1
host=192.168.10.51
dtmfmode=rfc2833
context=from-pstn

SIP\line2
Trunk Name:line2
PEER Details:
type=friend
secret=line2
host=192.168.10.51
dtmfmode=rfc2833
context=from-pstn

SIP\line3
Trunk Name:line3
PEER Details:
type=friend
secret=line3
host=192.168.10.51
dtmfmode=rfc2833
context=from-pstn

SIP\line4
Trunk Name:line4
PEER Details:
type=friend
secret=line4
host=192.168.10.51
dtmfmode=rfc2833
context=from-pstn

Outgoing Trunk:

SIP\line1
Trunk Name:line1
PEER Details:
type=friend
secret=line1
host=192.168.10.53:5061
dtmfmode=rfc2833
context=to-pstn

SIP\line2
Trunk Name:line2
PEER Details:
type=friend
secret=line2
host=192.168.10.53:5161
dtmfmode=rfc2833
context=to-pstn

SIP\line3
Trunk Name:line3
PEER Details:
type=friend
secret=line3
host=192.168.10.53:5261
dtmfmode=rfc2833
context=to-pstn

SIP\line4
Trunk Name:line4
PEER Details:
type=friend
secret=line4
host=192.168.10.53:5361
dtmfmode=rfc2833
context=to-pstn

Now, In the SPA-8800 I have each FXO designated with different Port numbers: 5061, 5161, 5261, 5361 for Line1, Line2, Line3, Line4

For the SLA: Here is the configuration for that aswell:

; defined SLA for Line1
[SIP/line1]
trunk => SIP/line1
station => SIP/10
station => SIP/11
station => SIP/12
station => SIP/13
station => SIP/14
station => SIP/15
station => SIP/16
station => SIP/17
station => SIP/18
station => SIP/19

;defined SLA for Line2
[SIP/line2]
trunk => SIP/line2
station => SIP/10
station => SIP/11
station => SIP/12
station => SIP/13
station => SIP/14
station => SIP/15
station => SIP/16
station => SIP/17
station => SIP/18
station => SIP/19

;defined SLA for Line3
[line3]
trunk => SIP/line3
station => SIP/10
station => SIP/11
station => SIP/12
station => SIP/13
station => SIP/14
station => SIP/15
station => SIP/16
station => SIP/17
station => SIP/18
station => SIP/19

;defined SLA for Line4
[line4]
trunk => SIP/line4
station => SIP/10
station => SIP/11
station => SIP/12
station => SIP/13
station => SIP/14
station => SIP/15
station => SIP/16
station => SIP/17
station => SIP/18
station => SIP/19

; Also you can see SLA infos via the CLI, by typing "sla show"

What am I missing from this? I know Im missing something....

Now, I am also frustrated due to the Lines not even being active now (Number Port Wait Time) But I don't even hear the relay "Click" @ the SPA8800. So, I have 2 Days to have this configured for testing on thursday when the PSTN Lines are active and ready for incoming/outgoing calls.



SkykingOH
Posts: 9678
 Member Since:
2007-12-17
Uncalled for? trixbox is
Tue, 12/06/2011 - 12:35am

Uncalled for? trixbox is out of date and abandoned. No updated in over a year and a half, no info from Fonality.

I can't understand why you would install this software instead of a supported distribution. Perhaps you were unaware? It was not meant to be rude.

All of those trunk entries don't make any sense. It's not needed. If the SPA is on a static IP it doesn't need to register or authenticate at all.

If you need to route each port separately use a CID prefix in the SPA.

Also the host field should only contain an IP, the port directive set the originating port.

--

Scott

aka "Skyking"



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.