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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

V6.1.5 Upgrade and now sip trunks not working.

Status
Not open for further replies.

IPmonkey

Technical User
Jan 5, 2004
234
GB
Upgrade of Inhouse IP500v2 generally went well until testing the voip.co.uk sip trunks we have on the system.
Typically they don't work and registration fails and I can't quite put my finger on what the problem is.
I also have Sipgate sip trunks and they are still working!

I copied the 6.0 sip config settings into my home system IP500V1 on sw 5.0.24 and sip works without any problems.

Jamie mentions in the 6.1 FT thread that his sip trunks didn't work following the upgrade!

Anybody else had problems, and if so what was the resolution.

Cheers

Monkey
 
Can you post a trace of the registration of the trunk?

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
There is a bug that after the upgrade the user name/password are gone on the sip trunk.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
If your SIP trunk does not need STUN, then you have to disable it.
Set network topology info to none. Setting this to lan1 or lan2 worked in 5.0 but not in 6.0 or 6.1. Depending on your connection method this can be a problem.
 
Albus2, this was already working fine on v6.0.18 and the network topology info was already set to none.

I managed to get it working by changing the port from 6060 to 5060, still not been in the office long enough to sort out the outbound.
But the Inbound was priority as our Isdn2 lines fall-over on busy to the sip trunks!

Monkey
 
OK. You did not jump from 5.0 to 6.1.

Just to mention strange SIP problems with 6.1.
One of our engineers did a new install with SIP trunks. They worked, but only one way speech depending on who initiates the call. The provider traced a malformed RTCP packet.
He downgraded the IPO to 6.0 and tested again. It worked without problems. Then upgrade to 6.1 again.
Guess what, it still worked. Nothing changed. But some of the new options were lost, like SNTP which is no surprise.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top