Gamma SIP Inbound problem

[slamminhammo]

I have a 500v2 at latest R9 software with some analogue trunks and Gamma SIP trunks.
the SIP works fine for outbound calls but fails on inbound as soon as the receiver picks up the handset.
Phone rings correctly but just no call can take place.
the router is a Draytek, which is being set up by others.
I hear they can have som eissues?
I have set the IP Office up just the same (with local site variations of course) as other Gamma sites, so I suspect the problem is on the Draytek, firewall as it is not allowing the RTP traffic?

Any help appreciated.
If you need more info on the IPO or Draytek I can provide that.
Thanks

Technolgy - The Mother of Frustration

 

[Gunnaro]

Are you sure it works outbound? Could easily be sent to the analogs if your ARS is not configured properly. Sounds like some ports are blocked (RTP) or SIP inspection / ALG is enabled on the firewall.

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

 

[jamie77]

Ditch the Draytek. They are always trouble. We actually now refuse to put SIP on them from past experiences. Google about, it seems well known.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[hairlessupportmonkey]

FYI there is a SIP ALG on the draytek you need to disable.

sys sip_alg ?
Checks if SIP ALG is enabled or not, if it is:
sys sip_alg 0
sys commit
sys reboot
Saves changes to the router and restarts the device.

ACSS - SME
General Geek

 

[slamminhammo]

Hi Guys
thanks for your responses.
Turned out to be a bug with 9.0.3.
Upgraded to 9.0.4 and all worked straight away


Technolgy - The Mother of Frustration

 

[jamie77]

Odd. We've a few sites with R9.0 and Gamma SIP.

Did you get this confirmed by Avaya, if so what was the actual bug problem and JIRA number??? Just so I can keep an eye out for issues.

If you just did an upgrade to see (not a bad thing!), then it may have been the full reboot that brought it back into life. Keep an eye on it as we've had a few sites with Drayteks and they work for a bit, then just crap out for no reason.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[amriddle01]

It's the NAT sessions timer Jamie, it needs reducing with the portmaptime -t 60 command via telnet

 

[jamie77]

Really???? Cool. Thats one for the memory bank.

We usually just get them to chuck it out!!!!

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[slamminhammo]

It's on the tech bulletin for 9.0.4.
Our distributor tech support pointed me at it.
I had a already rebooted many times.


Technolgy - The Mother of Frustration