# Q2687RD Voice Channel Problem

**URL:** <https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078>\
**Category:** IoT Modules\
**Created:** [November 26, 2024, 8:02pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078 "2024-11-26T20:02:59Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 26, 2024, 8:02pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/1 "2024-11-26T20:02:59Z")

</div>

I can’t hear the audio through the mic and speaker through the SP1 or SP2. I cant hear from the remote side, the dtmf tone that I can send through the AT commands, which I find strange.  
Originally, the equipment had a Q2687Classic installed, which was replaced by a Q2687RD.  
The firmware installed in the module is 7.52 and the functionality of the program in the module, is run normally, gpios checks status, etc.  
The problem is in the audio tx and rx of voice channel.  
Can I check any medition point in the module??.  
Regards

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 27, 2024, 1:23am UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/2 "2024-11-27T01:23:39Z")

</div>

did you compare AT+SPEAKER? command with the OK module?

BTW, it is strange that even DTMF tone cannot be sent out, I am wondering if this is network related issue, are you able to send SMS or receive SMS in module?

---

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 27, 2024, 1:23pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/3 "2024-11-27T13:23:30Z")

</div>

Thanks for the answer. Yes, I have checked the speaker selection, according to the connection. I’ve worked with the modules since q24, I have some experience, that’s why I’m struck by what happens, especially that the tone doesn’t come out.  
My idea was to try to rule out any internal problems in the module, since the general functionality would be ok.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 27, 2024, 1:31pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/5 "2024-11-27T13:31:13Z")

</div>

are you able to send SMS or receive SMS in module?

---

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 27, 2024, 1:36pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/6 "2024-11-27T13:36:32Z")

</div>

I have tested the chip in a q24 module and it works ok. In case there was any kind of restriction on the part of the company. The module is enabled, the program runs normally. Why does it ask me if it sends SMS?, how do you associate it with the voice channel

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 27, 2024, 1:49pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/7 "2024-11-27T13:49:30Z")

</div>

it is strange that even DTMF tone cannot be sent out, I am wondering if this is network registration related issue

---

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 27, 2024, 1:54pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/8 "2024-11-27T13:54:40Z")

</div>

It’s very strange. I can answer the incoming call, I see the message that the voice channel is opened and I can’t hear anything.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 27, 2024, 2:07pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/9 "2024-11-27T14:07:02Z")

</div>

So with same firmware and OAT application, q2687classic is working but not for q2687rd?

Do you have the q2687 dev kit?  
You can isolate if this is hardware issue

---

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 27, 2024, 2:08pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/10 "2024-11-27T14:08:48Z")

</div>

No, not working in any type.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 27, 2024, 2:10pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/11 "2024-11-27T14:10:34Z")

</div>

Then it could be hardware issue

Do you have the q2687 dev kit?

---

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 27, 2024, 2:13pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/12 "2024-11-27T14:13:10Z")

</div>

> [@jyijyi](#):
>
> Then it could be hardware issue

I don’t have the dev kit, I have a board where the module was installed in service

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 27, 2024, 2:24pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/13 "2024-11-27T14:24:50Z")

</div>

How is the testing on that board then with same firmware and OAT application in2687classic and q2687rd?

---

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 27, 2024, 2:30pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/14 "2024-11-27T14:30:56Z")

</div>

The version of firmware are differernts for the type of modules.  
I dont understand…

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 27, 2024, 2:31pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/15 "2024-11-27T14:31:40Z")

</div>

Didn’t you can change the firmware?

---

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 27, 2024, 2:34pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/16 "2024-11-27T14:34:53Z")

</div>

I’m looking on eBay to buy another module… I don’t have a local supplier

---

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 27, 2024, 2:37pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/17 "2024-11-27T14:37:53Z")

</div>

The installed firmware was the same as the one that had been installed in the module in serviceI doubt the hardware, but I find it strange that only that fails, so I wanted to see if there was any measurement to rule out that problem

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 27, 2024, 3:00pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/18 "2024-11-27T15:00:23Z")

</div>

how about OAT application?  
Are they the same?  
Have you ever tried to stop the OAT application by AT+WOPEN=0 to see if there is any improvement?

Have you tried more Q2687RD to see if all of them having the same problem?

---

<div class="post-metadata">

**Author:** ![capsl2007](https://avatars.discourse-cdn.com/v4/letter/c/90db22/32.png) [@capsl2007](https://forum.sierrawireless.com/u/capsl2007)\
**Post date:** [November 27, 2024, 3:08pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/19 "2024-11-27T15:08:20Z")

</div>

My doubt is because I have tested the modules on the same board. and the same thing happens in both modules. The OAT has been compiled with different IDEs, one was the same as the q2687Classic module was in service and the other has been compiled in the software that I have recently installed due to the different hardware version, etc. That’s why I don’t know if the board could have caused some damage to both modules when inserting them or what could have happened… So I wanted to know if there was a way to test the module in some way.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 27, 2024, 3:18pm UTC](https://forum.sierrawireless.com/t/q2687rd-voice-channel-problem/34078/20 "2024-11-27T15:18:35Z")

</div>

quite confused…

anyway, you better do some more test first to isolate if this is hardware issue
