Gamma SIP via Meraki MX84

[MMWTEK]

Hi

Iam having an issue getting Gamma sip trunking working via Meraki MX84 firewall.
The ip office v2 is on 8.1 ( 69 ).

I have tried various settings within Network toplogy to get the ip office to send
out the public ip but it still just sends the internal add of the ip office Lan port.

I tried Firewall / Nat type - Static port block
Binding - 60s
Public Ip - x.x.x.x
Udp - 5060

Then set within the transport tab to use the required Lan port.

I then tried open internet / full cone nat / Unknown. Still showed the internal add.

I played arround with using a stun server ( 77.72.169.164 ) but know Gamma dont support this. I got incoming calls to work with audio both ways but couldnt dial out - waiting for line - Gamma advised the pbx was sending bye request.

In summary Avaya have advised me to upgrade to 8.1 ( 95 ) and iam going back to site this week. Iam going to try setting it using
Static port block - 60 - pub ip - 5060. Iam not wanting to use a stun server so just looking for any advice on what to try within the network topology to get the ip office to manipulate the header for the public ip.

Any advice appreciated and if anyone has got this working with a Meraki at this older version 8.1 . I will get traces etc when
iam back.


Thanks

M

 

[critchey]

I do remember having some issues with SIP on earlier versions of R8.1. I actually do not use R8.1(95) as I remember someone telling me it had some pre-release code for R9 and was buggy. I use to use R8.1(85) but I had a colleague run into some issues with a system on R8.1(85) and having over I believe it was 40 users... You could try R8.1(91) if you want I am unsure if that is a mess or not. You may want to advise the customer to upgrade since R8.1 is getting fairly old and was pretty buggy start to finish to be honest.

The truth is just an excuse for lack of imagination.

 

[ipohead]

I can't help on the Meraki but the settings I have here for Gamma on R8.1(69) are

Network Topology
STUN server 217.10.68.152 this is Sipgate as Gamma don't support
STUN port 3478
Firewall/NAT port restricted cone NAT
Public IP address x.x.x.x
Public port 5060

 

[TheSmash]

Are you using Port Forwarding or 1:1 NAT on the MX?

ACSS (SME)

 

[MMWTEK]

Hi

Thanks for the replies , appreciated

Ipohead - I will try those settings before I do the upgrade to 8.1 ( 95 )

TheSmash - Its port forwarding thats setup on the Meraki as per Gammas rtp range / ip office range.



Thanks

Michael

 

[MMWTEK]

Hi.

If I managed to get this working using a stun server would you say this would be safe enough
and reliable for the customer. Just wondered with Gamma saying they dont support stun and
if any service risks etc.


Cheers

M

 

[derfloh]

Never worked with Gamma. But what I hear from them sounds ridiculous to be honest. Never had to do port forwarding with any other SIP provider.

Need some help with IP Office?

https://www.fwilke.com/home

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[TheSmash]

Gamma can be a pain, especially with pre-9.1 IPO where SIP could be a bit flakey.

Key things with Gamma - they look at the whole SIP packet, and if the Public IP isn't in all the contact/From fields etc, then they will reject the call. As such you need to make sure that the IPO rewrites these to remove the private IP. The best way to do this is with Network Topology and setting your Public IP. Then setting the Gamma Trunk to use Network Topology Lan1/2 accordingly. This was a bit flakey before 9.1 though and sometimes didn't work and you had to set up STUN.

On the MX I use 1:1 NAT and use a spare Public IP. You can lock this down to just the Gamma sig and med servers providing you with security.

ACSS (SME)