Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - cabarrushealth

Pages: [1] 2
1
Hello Folks,

We have an employee who has a LG V30 on ATT  and the latest MiCollab app running Android 9 OS. When we dial them a notification banner will be displayed for a second and then disappear which doesn't allow them to answer the call. The person dialing them will hear a ring till the employees voicemail picks up. I was wondering if anyone has seen this issue before and have a known fix? Any help would be appreciated. Thanks

2
Thanks for the reply....

I must of been a half a millimeter from it not being slid in all the way. I adjusted the two brass screws and pushed it in that tiny bit more and it worked.

3
Hello Folks, this one seems pretty simple. We've purchased our first 6900 series DECT Headset (Have two now) and tried on multiple 6930's and its never detected. I connected to the one 6940 we have and it works great. I posted some pics below - what am I missing? Thanks

6940
https://i.imgur.com/IK9rM0o.jpg

6930
https://i.imgur.com/2Dtn4sq.jpg

4
We're starting to see this issue and loosening the screw i circled a bit seems to fix the problem for us.

5
Hello Folks,

We have staff that utilize the softphone which is part of the MiCollab Client for Windows. When their in the office they need to select Settings -> General -> Use Teleworker (uncheck) and out of the office they need to check it. Is this what other organizations are required to do? It just seems like automating this somehow would save our end-users from needing to perform this additional step.

Any feedback would be appreciated.

Thanks!

6
Mitel Software Applications / Re: Collab Client on Iphone
« on: January 04, 2021, 09:56:50 AM »
Answers\Applications\MiCollab Release Notes?

If you could give me specifics, that would be helpful to me. thanks!

7
Mitel Software Applications / Re: Collab Client on Iphone
« on: January 01, 2021, 01:35:20 PM »
Hello, Where would I find "Known Issues" like the one you posted? Thanks

8
I did make Send options keepalives is set to "Always" but ill change it back to "Only behind a NAT" .

I tried to get the set to TCP but was having issues with it registering properly but it seems like its something I need to look at again.

Which specific Tug log should I be looking at, there are a few that begin with Tug.

I attached a couple of call flows , its still left to right - Internet - MBG - MiVB . I'm not sure if they help any.. Thanks again..

9
Thanks for the quick reply, I didn't pay attention to the timestamps so what you say makes sense.

It does look like its behind a NAT as the Connection IP and Registration IP are different under SIP profiles and devices.

Send options keepalives is set to "Only behind a NAT" but should I change it to "Always" ?

The transport for the set is set to TLS under SIP profiles and devices. Under System -> Settings UDP and TCP Protocols are checks as well as TCP/TLS though. Does it look like its set to UDP? Thanks

10
dilkie, I went ahead and created a ladder diagram on one of the calls our user lost voice in. The blue call is one that ended properly and the yellow is one that had the voice issue. Left is internet, middle is MBG, right is MiVB. It looks like a Request Timeout between MGB -> MiVB but I'm not understanding the BYE before that.

11
You folks are awesome, thanks for all the feedback. Ill let you know how things progress..

12
thanks, ill take a look..

Can these events cause the one way audio and if so is there anything I can do to fix it?

comment:excessive jitter, rtp packets queued:30

13
lunda - When I enable "Relax set RTP checks" the KPML wants me to put a "Confirm KPML password" to match whats in the field currently. I'm not sure what do put here?

dilkie - Could you provide me more specifics on the signaling trace and where I would find that? Would it be in a specific log or event?

Thanks both for you feedback!

14
MBG   sip call terminated   terminated   Warning   Mon 21 Dec 2020 15:40:26 EST   dn:1234, call-id:9228057663e8cc65, reason:INVITE transaction timeout (dlg 2974), icp:X.X.X.X

I think those errors are lining up with the calls having the issue.

15
Thanks for the feedback so far.

The MiCollab users are connecting to MGB in DMZ. I know MiCollab for Mobile uses SIP but we have PRI trunks via the 3300, I'm not sure if that answers the question?

I'm not sure if I can check those logs unless I have SIP trunking?

Pages: [1] 2