@Col_H 

You can consider upgrading the firmware:

https://support.omadanetworks.com/en/product/dr3650v/v1/?resourceType=download

 

And monitor if this persists. 

  @Col_H 

 

Thanks for that, i did try and find an upgrade package but could not locate it.

 

Anyway, carried out an upgrade and re-tried. Same result.

 

Double checked via outbound calls by using another phone, and tried various other mobile phone numbers / providers so it all points to TP Link router/switch.

 

I am guessing that the signals for ringing etc are being misunderstood and/or confused by the TP Link router/switch. I would monitor but I have no idea what the handshaking should be etc.

 

On the other side of the fence TP Link should check that there router /switch works, as I am guessing this is all common by protocols. 

 

Will try and contact them but not holding my breathe.

 

 

you will need wireshark for that to catch call flow. i suggest to mirror traffic on that switch port and see what is goin on

  @Col_H 

Col_H wrote

  @Col_H 

 

Thanks for that, i did try and find an upgrade package but could not locate it.

 

Anyway, carried out an upgrade and re-tried. Same result.

 

Double checked via outbound calls by using another phone, and tried various other mobile phone numbers / providers so it all points to TP Link router/switch.

 

I am guessing that the signals for ringing etc are being misunderstood and/or confused by the TP Link router/switch. I would monitor but I have no idea what the handshaking should be etc.

 

On the other side of the fence TP Link should check that there router /switch works, as I am guessing this is all common by protocols. 

 

Will try and contact them but not holding my breathe.

 

 

As someone has already noted, this requires a far more detailed investigation based on the transmission (Wireshark). 

 

There are successful cases for VOIP config and they dial outbound fine. 

As the service is online, it can contact the ISP server. The phone call receiver only got a ring; this needs at least two Wiresharks. I think you can do the Wireshark on the Omada gear site first, which is how we determine if the outbound traffic to ISP is okay. If that's okay, the other end only got one ring, the issue might not exist on our gears. 

  @Clive_A 

 

Hi,

 

I have passed this over to TP link Technical Support, as you are all correct. This issue is way above the normal fault finding requirements by the user. This is not a DIY home solution or network, mix and match etc, it should be proved and tested by the manurfactor. Not by us.

 

Unsure if I am the first to use these onboard ports?. There is no feedback from anyone saying "I have these working", so its a big question. Either way the set-up should be simple stuff as it has limited inputs etc and nearly plug and play. General ATA use the same varibles..

 

Ultimately, if TP Link cannot supply a solution, then they will have to issue a refund under the sales and goods act, and recall all the models as it will not work as per description.

 

They took ownership of problem this morning, and requested screenshots of VOIP-caller logs etc sent. Will keep you all in loop when I get some feedback.

 

 

 

 

  @Col_H 

Col_H wrote

  @Clive_A 

 

Hi,

 

I have passed this over to TP link Technical Support, as you are all correct. This issue is way above the normal fault finding requirements by the user. This is not a DIY home solution or network, mix and match etc, it should be proved and tested by the manurfactor. Not by us.

 

Unsure if I am the first to use these onboard ports?. There is no feedback from anyone saying "I have these working", so its a big question. Either way the set-up should be simple stuff as it has limited inputs etc and nearly plug and play. General ATA use the same varibles..

 

Ultimately, if TP Link cannot supply a solution, then they will have to issue a refund under the sales and goods act, and recall all the models as it will not work as per description.

 

They took ownership of problem this morning, and requested screenshots of VOIP-caller logs etc sent. Will keep you all in loop when I get some feedback.

 

 

 

 

1. You can have outbound calls, which already indicates the router to the provider is fine. Provider to the receiver is okay as well. That's what I find strange about. It shows the registry is successful

2. If you can't access Wireshark, then you are required to remote with the support team. I am asking you to provide it on your own because certain users prefer not to remote on their desktop. And I don't offer remote access on the forum. 

3. If you think that does not fit the description, it is your choice to refund or return based on the return policy. Recall or other actions are not my call.

4. My information source is not limited to the forum but also includes others. We have calls, chats, emails, forums, and other forums. 

And I also browse different subreddits from home and the business network for information and knowledge. I've seen similar cases, but most don't get back to us or the support which would be a problem with the provider or get self-resolved. But to get more accurate conclusions, one needs to see the Wireshark result, config, and hardware connection. 

 

TBH, your description so far, I believe most people would not give any concrete answers if you try out on subreddits like homenetwork. Simply suspect that would be a config problem. 

  @Clive_A 

 

Thank you, you acknowledged that it all points to the unit. As you stated it registers, all ok. Upon an outbound call it either rings the mobile once and goes engaged, or to a landline it will ring and upon pick up it gest disconnected and goes to a high pitch tone. There the hole widens?

 

Also the unit does not function, out of the box, as per the sales brochure, that raises a question mark. Either way, I thought this would be simple to resolve. You must, or maybe have working units. If so, go on line, prove it, do a firmware comparison to mine, maybe hash it, and lets prove it all works. Simple.

 

Then a fault finding path can begin.

 

Hopefully your tech team will come up with a solution, oen way or another.

 

 

 

 

 

 

 

 

  @Col_H 

 

TP Link have been workinhg on this for a couple of days now. What I question, it probally takes 1 hour to find a unit, say 1 hour to set up and 1 minute to see if it all works.

 

Sadly like in many cases silence speaks volumes, and no idea whats going on. Within a few hours someone should of been calling me and saying, look this is what we have found..

 

 

It also raises the question, what else does not function correctly?

 

 

 

 

 

 

  @Col_H 

 

To All,

 

The issue has been passed to R@D, hence I have asked for a full refund as the unit does not operate as per fuctionallity description.

 

Also asked for supply chain to advised as others might have same problems as myeself.

 

It also raises another question as what else does not work and can you trust the unit?

 

Will keep all in loop.

 

A bit worrying.....

 

 

 

A quick update as its been a while.

 

TP Link R&D could not provide a solution, but sugguested changing the MTU. And also confirmed to return unit.

 

Brought another unit from a well known manurfactor, unboxed it and worked first time. 

 

So the experiance ends here with the first item of TP Link tried, returned.