3cx supported snom firmware - late publish

[Kiwi_at]

Hey there,

with 10.1.37.11 there is an problem that mfv is not working correct. Snom fixed this issue in some newer firmwareversions some months ago.
Altough 3cx isnt supporting this new firmware. How long is the gap between vendor offers a new firmware and 3cx is supporting it?

Thanks!

 

[JohnS_3CX]

Hello,

There is no standard timeframe, vendors need to run their tests and we need to run ours to make sure it is as good as possible before the 3CX version is released.

By the way, when you said MFV, are you facing issues with in-band DTMF?

 

[Kiwi_at]

Since 10.1.37.11 there a two new releases :-(

yes i mean DTMF, sorry! MFV is the german word.

 

[JohnS_3CX]

No problem. What issues did you face with DTMF? If you want you can describe your scenario and it may be something we can help you with

 

[Kiwi_at]

check this link: https://service.snom.com/display/wiki/10.1.39.11+Release
Correction: SAP-3489

 

[JohnS_3CX]

Ok looks like the in-band only is affected. We don't use inband in our provisioning but rather use RFC2833 which goes through the SIP signalling and is much more reliable. So this should not affect 3CX Snom extensions.

If you call 3CX IVRs you should be fine, if you call outside the PBX and your provider supports RFC2833 again you should be fine.

 

[Kiwi_at]

we call outside our pbx, but it only works when we restart the snom before, so it sounds like this issue in the changelog :-(

 

[JohnS_3CX]

Can you tell me which provider you use and whether you have custom templates on the Snom?

 

[Kiwi_at]

we use NETPLANET and no custom template

 

[JohnS_3CX]

Ok so using the default 3CX templates and NETPLANET as a provider I can confirm that RFC2833 is supported.

The Snom link above says in SAP-3489 that only in-band stopped working however. This should not normally affect your DTMF, the phone sends it in RFC2833 by default.

There is a way to confirm this of course. I can explain how if you want to check it, you just need access to your management console, and a Snom that the DTMF stopped working. Do not reboot the Snom! It must remain running for days until the problem appears and then you can run the test.

 

[Kiwi_at]

yes please explain me - would be very nice

 

[JohnS_3CX]

Sure thing:

1. So you wait until a Snom phone starts having the problem. Don't restart the phone!
2. Then you start a capture, and call your voicemail for example from that Snom phone
3. Press some buttons, I suppose at this point the voicemail will not respond because the DTMF was not sent.
4. End the call, end the capture, click to download it and open it on WireShark.
5. On a good phone that works, you will notice RTP (telephone-event) DTMF {number pressed}
6. The sip message appears as RTP EVENT. This is what a working phone will send normally:

A phone that has the problem however, will not send those events unless you restart it. You can repeat the exact same test but instead of calling VM, call outside to another number that has a DTMF-based menu. If your capture shows that the RTP Events are sent, then you can be certain that your phone is healthy. In this case, the problem might be the recipient's provider, after NETPLANET sends the DTMF to them.

I believe that in such a case, NETPLANET support can also check and confirm for you that they send the DTMF from their network to the recipient.

 

[Kiwi_at]

yes thats true, the phone sends no RTP and no RTP Events. When you restart you can see rtp and rtp events.

 

[JohnS_3CX]

What model Snom are you using? I would like to check ours here too.

 

[Kiwi_at]

We are using Snom D745 system-wide

 

[JohnS_3CX]

Thanks, we are waiting to receive the newer firmware which should resolve the issue. Unfortunately I cannot tell yet when we will be receiving it.