Community

Content

Page tree

I have connected an M700 to a Grandstream UCM 6304A in order for my customer to take advantage of the M80 handsets for use outdoors.
I have set up the system on my bench and tested everything. I have everything working the way that I wanted. One of the features that the customer most needed was the ability to park calls.
Grandstream allows this using the #72 Feature Code.
I happened to notice just before packing everything up to take to the customer that I had forgotten to update the firmware on the M700, M70, and M80’s.
The M700 was running v4.10 when I got it. I cannot recall what versions the cordless handsets were running prior to updating them.
I have the M700 updated now to 520.2 and all of the handsets running 650.2. Now that I have performed the firmware updates the cordless handsets are no longer able to use #72 to park a call consistently. Sometimes it works without issue, other times I have to enter #72 two or three times before it works. 

Has anyone encountered any issues with sending touch tones to an onsite PBX following the firmware updates? I'm assuming that this would be related to tones. I don't really have any better ideas for why this isn't working consistently.
I tested this several times before updating the handsets to 650.2 and hadn't noticed any issues with initiating a call park via feature code. 

profilePicture

Kevin Davison

End user

Joined: 26.04.2023

2 Comments

  1. Snom Federico Rossi

    Hi, I think the first thing to do here is to upgrade the M700 to firmware 530b10 and downgrade the M70/M80 to the same firmware version. If you use different versions on handset and base, there may be incompatibilities and I don't exclude that they could lead to the problem you described.

  2. End user Kevin Davison

    I opened a support ticket with SNOM and they gave me the same advice. Unfortunately that didn't resolve the issues. 

    I did experience the issue while setting the equipment up in my office. I updated the firmware (to incorrect versions) and the issue disappeared. 
    After taking everything onsite the issue appeared again and support advised getting everything to 530b10 but it didn't solve the problem. 


    The customer worked with the system for a few days with the behaviour that was described and asked that it all be removed. I guess I'll have to try and find it a new home.
    I've placed all of the equipment back on the test bench here and have been unable to duplicate the issue since. I'm assuming that it's being caused by excessive noise on the customers PSTN lines, or interference from their two-way radios, or something else that I didn't get the chance to troubleshoot.