Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP GWs with IPO 9.0

Status
Not open for further replies.

yankblan

Vendor
Jun 17, 2010
831
CA
As detailed in an older thread, my Cisco (Linksys) SPA3102 VoIP gateways stopped working after upgrade to 9.0. Two different guys testing on two different lab systems, still not working. I'm currently trying the same scenario with a Mediatrix 3208, no go. We ordered an Audiocode for testing, should get it soon.

Anybody else experiencing similar problems?

ACSS-SME

 
As mentioned before i did not see it but i did not try it either.
But did you try using it as a phone instead of a trunk?


BAZINGA!

I'm not insane, my mother had me tested!

 
I have a colleague who installed an Audiocode FXS and it works,so I suspect configuring either of my devices as FXS would work too; just don't have a 3rd party IP license in my demo; could get it easily enough though.

But even if it works, it doesn't help me, since I need to send a trunk to the IPO through SIP, so configuring it as a phone is not a solution.

ACSS-SME

 
Why? it is an ATA.
A total different story:

On 9.0 i connected Android and iPhones to our server edition.
The Androids worked fine straight away.
The iPhones did not because our SPA3102, that is only use for some port forwarding, blocked the port 5060 on TCP.
The android phones use the secure connection option which uses TLS.
I changed port 5060 to 5070 on the remote site and it worked again.
So perhaps you use TCP and TCP is blocked because of the SIP ALG that the SPA3102 uses somehow.
Try setting the SIP trunk on the IPO on port 5070 and on the SPA3102 too and try again.


BAZINGA!

I'm not insane, my mother had me tested!

 
The trace in your older thread shows REGISTER SIP messages coming from your SPA3102. If you do not want to set it up as a client, then it should not be programmed to register like a client. I am not familiar with the SPA3102, but it should have the IP Office set as the outbound proxy only and not as the Registrar.

With IP Office 8.1, IP Office would ignore REGISTER requests that came from the same IP address that is programmed as a SIP trunk. With release 9.0, it now responds to REGISTER requests where as before it would not. This change may be causing the breakage.

If you cannot prevent the SPA3102 from sending register requests, you may have to set it up as a client on the IP Office side, or turn off SIP Registrar on the IP Office LAN settings if SIP clients are not being used.
 
Interesting. But I did turn off every settings that I did not use for testing, tried turning off registration on IPO side, proxy, ect.

I'm at close to 100 reboots of just trial and error on the different modules. I will try different ports, but it does the same on SPA and Mediatrix, so I know its IPO's fault, not the gateways.

I'll let you know how it turns out

Btw, it didnt register at 8.1 either, but SSA showed idle, now I have a big red OOS alarm

ACSS-SME

 
Don't know what it is. When to bed past midnight Thursday working from home through VPN. Got to the office Friday morning, was still not working, so I head out on the road. A colleague of mine did some testing, didn't change any settings, and it started working.

We'll be testing the SPA with these settings when I get it back.

ACSS-SME

 
Update: it is now working, and configs are pretty different on both the SPA and the IPO.

redphone you were right about the registration part, it was one of the problems we encountered.

ACSS-SME

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top