"SIP Streaming in progress, RTSP Streaming is not allowed, try after some time !!!"

[Brigitta]

I recently purchased 2 new Essential Spotlight cameras and although they are functioning normally and sending me notifications, but I cannot livestream the feed. I continually get the above-referenced error code or "This camera is streaming on another device and cannot be accessed right now" - even though I'm the only active user trying to retrieve the feed when I look under active users. What can I do to livestream on these cameras? 

[BrookeN]

This behavior should now be resolved. If anyone within this thread is still seeing it please let me know. 

[BrookeN]

The development team was able to reproduce the issue as described and is continuing to work toward a solution. As soon as we have more information available, we'll post an update.

[BrookeN]

I have passed this onto the development team and let them know the error you are seeing as well. I will reach back out as soon as possible. 

[Readytorun13]

My phone isn't ringing when doorbell is pressed, so I restarted doorbell. Now it's giving me SIP streaming in progress error.

[BrookeN]

I have passed this onto the development team and let them know the error you are seeing as well. I will reach back out as soon as possible. 

[CABRON]

The question is why? ARLO knows about problems with these camaras . They dont care as long as we keep buying. Let me remind you we purchase this as a security item not to be amused or a play thing. Same problem as others SIP cant stream. Maybe FCC can help you find a fix

[CABRON]

So after troubleshooting the SIP/stream problem i found out that:

1. I had to remove my private DNS from my router.

2. I had to allow ARlo and who knows who access to my network thru 443/80. 

3.I have to lower my security to let ARLO do its job. What a joke. 

No wonder we get hacked left and right. 

[StephenB]

---

@CABRON wrote:

2. I had to allow ARlo and who knows who access to my network thru 443/80. 

---

Unfortunately Arlo support tends to ask people to unblock these ports when they reach the end of their troubleshooting script w/o finding a solution. 

Try undoing that change and test again.  The Arlo equipment only makes outbound connections to ports 80 (http), 123 (NTP), and 443 (HTTPS).  There are never any unsolicited inbound connections.

Proxies on these ports could fail, so it can be necessary to forward ports to bypass the proxies. 

---

@CABRON wrote:

1. I had to remove my private DNS from my router.

---

How many DNS servers are advertised to DHCP clients?  Someone reported a bug a while ago, saying that the equipment stopped working when the server list expanded from 3 to 4.  No idea if Arlo fixed that. 

[BrookeN]

The development team was able to reproduce the issue as described and is continuing to work toward a solution. As soon as we have more information available, we'll post an update.

[Mavr88]

 same error started happening to me a couple of days ago. This happens every time someone rings the doorbell and the call gets answered. Can't live stream after that and as someone said in this post, the error clears like 30 minutes later. However the camera becomes completely unsable after a call

[alan-v]

I’m having the same issue with my driveway camera. I’ve had this for over five years and I’ve never seen this message before. These cameras are too expensive for stuff like this to affect so many people

[krisapap]

Hi, I have the same problem when I am connecting a new doorbell. How I can fix this issue?

[My1971]

Hi, I have the same problem. Fix this soon! 

[Kurant]

So let me get this straight... 

MULTIPLE people have this issue which has left cameras rendered useless and still paid you every month while you take this long to fix the problem.

In the meantime, your subscription per month price is going up 60%?

You're kidding me, right? I've paid you thru quality issues that took MONTHS to fix. It took months for you to even admit there was a problem - all the time blaming my internet and router. I'm paying you now, and I have 5 cameras and the only thing not getting this issue is my doorbell. What are we doing here?

[BrookeN]

I just wanted to give you an update that a fix for the behavior you are seeing will be within the week. I will update the community as soon as the development team has deployed that fix. I do appreciate all your patience as we have worked on the behavior you are seeing and I do want to apologize for any frustration that it may have caused. I will be in touch soon. 

[BrookeN]

This behavior should now be resolved. If anyone within this thread is still seeing it please let me know. 

[Mbart00]

Still having this issue.