Problem with SIP-Trunk

big-net
Getting noticed

Problem with SIP-Trunk

Hello,

 

since we switched to cisco meraki we have had a problem with our sip-trunk.

Inside our network we have a pbx which set up the sip trunk to our provider.

Mainly at night, if not so much is called the problem appears.

 

The registration of the sip trunk possibly get lost.

when the PBX registers again with the provider, everything works fine.

 

Whats the problem?

Any help is appreciated

 

thanks Oliver

9 REPLIES 9
UCcert
Kind of a big deal

Sounds like the SIP Keepalives are being lost/dropped.

 

Do you have SIP-OPTIONS enabled as this will frequently talk to the provider to keep the SIP Trunks up?

Darren O'Connor | uccert.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
big-net
Getting noticed

Thanks for your reply.

 

Where can i find this option?

We have a MX250.

UCcert
Kind of a big deal

It’s on your PBX or SBC whichever you’re using to register the SIP trunks 

Darren O'Connor | uccert.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
big-net
Getting noticed

Yes, but with our old Cisco ASA everything works fine.

The Problem starts since we switched to Meraki.

Nothing has changed on the PBX

UCcert
Kind of a big deal

Have you run a wireshark trace out of hours on the MX to see what’s happening?

Darren O'Connor | uccert.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
big-net
Getting noticed

No not yet.

Since I don't know when the effect will occur, I would have to run the wireshark permanently.

i think there is a huge trace file in the end

PhilipDAth
Kind of a big deal

Don't use SIP/UDP.  Change to SIP/TLS, and if you cant do that, SIP/TCP.

We are using SIP/TLS.

Hallo,

i have found the following statement about a UDP timeout:

https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/VoIP_on_Cisco_Mer...

The MX does have a simple UDP timer function, which will drop a traffic flow after an extended period of inactivity. This timer cannot currently be changed. However, a timeout would require both peers to be completely silent for an extended period of time in order to take effect. UDP communication between peers on an active call, for example, is highly unlikely to be dropped due to a timeout.

is this may be causing the error?

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels