[tagapache]

I have a bank of spa3K's operating as pstn gateways between an asterisk pbx and a bunch of centrex lines. Everything works fine except the fact that I can't get the spa to pass centrex command sequences up the line to the centrex exchange. The commands have the form **nn. Asterisk happily despatches the command sequence to the spa but the spa chucks it back with

WARNING[10924]: chan_sip.c:6864 handle_response: Forbidden - wrong password on authentication for INVITE

It almost looks like the spa is attempting to route the command back to asterisk. The dial plans in the spa are just set to xx. to allow asterisk to handle dialing/routing issues.

Any suggestions guys?

[RobT]

The commands have the form **nn... The dial plans in the spa are just set to xx. to allow asterisk to handle dialing/routing issues.

How about a dial plan like

[x*][x*]x.

[Woodland]

I'd like to echo arielb27's post above. I replaced the SPA3K in it's FXO capacity with an Asterisk@Home server with a TDM400, very nice.

However, as we have no current need for the 3K's FXO port, I'd like to turn it into basically a SPA2k with LIne1 & Line2...

I have Line1 working wonderfully as a SIP extenison off the A@H server.

I have the PSTN line registering, but if I try to call it from another extension, I get 503 Service Unavailable. If I pick up the phone attached to it, I get dead air.

Is it possible to configure the PSTN port as Line2, or should I just shelf the 3K until I need another PSTN line?

Thanks!

[tagapache]

[x*][x*]x.

same result I'm afraid. Made no difference. Ishould point out that short local numbers and stuff like operator call (100) go out quite happily through these lines, but not **x.

[RobT]

Then in all likelihood you either have forgotten to remove all the star feature activation codes from the SPA's configuration pages (so the SPA is trying to interpret your star codes itself and then trying to send the relevant SIP message on) OR you have a problem somewhere earlier in your dial plan.

For example, my own SPA3000 works well with this element in my dial plan

[*#]78S0<:@gw0>

which allows my family to use two of the feature buttons on the telco supplied handsets just as they did before I put all the house extensions through the SPA. (I did require making sure that there are no conflicting codes in the "Vertical Service Activation Codes" section of the "Regional" tab of the SPA3000's configuration.)

Hope that helps

Rob

[mberlant]

Woodland,

The PSTN Line is an FXO port, which means that it listens for Dial Tone and Ring Signal from the other side.

A telephone set is also an FXO device, listening for Dial Tone and Ring Signal from an FXS server like your phone company.

Two FXO devices cannot interface directly with each other, as they are both listening.

[tagapache]

Thanks for this Rob. It's definitely an spa3000 problem because we tried a TDM400 on two of the lines and it worked perfectly. We also checked the vertical activation codes and none conflict - are you suggesting we should remove them?

We'll give it a go and see what happens.

[digulla]

Originally Posted by PhoneBoy

...
PSTN Tab:

SIP Credentials (Proxy, User ID, Password) point to an extension in sip.conf. This allows the SPA3000 to make a call to the * box as well as allow the * box to call the SPA-3000.
....
VoIP User 1 Auth ID: user
VoIP User 1 Password: password
VoIP User 1 DP: none (this means pass whatever the remote end sends)
...
[54]
secret=whatever
callerid="PB SPA3k PSTN" <54>
...
Also in sip.conf, I also have an entry to make outgoing calls via the SPA3000:

[pstn-spa3k]
type=peer
auth=md5
secret=areyououtofyourmind
username=pinky
host=spa3k.phoneboy.com
fromuser=splat
port=5061
dtmfmode=rfc2833
nat=no
context=home

In extensions.conf I have:

exten => _#9.,1,Dial(SIP/${EXTEN:2}@pstn-spa3k,60,tr)
exten => _#9.,2,Playback(abandon-all-hope)
exten => _#9.,3,Congestion.

How are all those usernames and passwords related? Somehow, the SPA must authenticate itself with *, right? So I would guess that at least some of them must be the same.

But when I read your documentation, I get the idea that I need to setup three different, unrelated accounts. I would expect to have two pairs: One for SPA which registers with * and one which allows the * to dial on the SPA.

Can you please explain this setup?

[dano3131]

Help me see the light please?
I got a SPA3000 and a friend has a Asterisk server what i want to do is have my PSTN line auto forward through the SPA-3000 to a specific VoIP on his box right now I call the PSTN the SPA3000 awnsers then I get a fast Busy can the SPA be configured to auto forward and or do I have to
put special commands into the Asterisk server to handshake with the SPA?

Can someone please show me the light in SPA / Asterisk for dummies lingo ? thanks.

[mberlant]

dano3131,

Please continue in your other thread. Crossposting just confuses everyone and makes it harder to help