webRTC issues

[Musarano]

Hi.  This is also what i have in windows firewall, if you can give us an advice on this too, we will appreciated it !!

We are also using RDPGuard windows app software, to try to block some more attacks too.

 

Hope this helps.

-M

[Musarano]

Hi

The two of the list are for the VodiaPBX Firewall i have as settings.

[Vodia PBX]

I would just whitelist the pbxctrl.exe with the Windows firewall. Then you don't have to list each separate port.

While you are on it, I would delete the FTP port (unless you want to use Polycom phones in the LAN) and possible also delete the TFTP port unless you want to use option 66 in the LAN.

[Musarano]

Thank You Sup!

One more question:

By having a domain name instead of the localhost, will i be avoiding this kind of attacks from passing forward vodia and at the same time WEBRTC keep working still?

 

Thank You

[Musarano]

 

I also mean, im having this kind of attacks and many other combination of it now :

<sip:a'or'3=3--@localhost>

<sip:00148223071956@localhost>

But i have an IVR not allowing to go directly to a far end extension to make someone getting crazy there.

Extensions are behind another remote PBX, im using Pattern and CallerId Pattern together to make the webrtc call be responded unless it comes directly from the webpage. (i presumed), so i wont exhaust the remote PBX available lines limitation.

Will this functionality would keep going if i use a domain name other than localhost one?

 

Thank You

[Musarano]

Hi, Nevermind the prev. question. im already testing the modality.

One question i have is, that after i created a new Domain+Account+Extension,

This is how it looks at the rightmost side under VMail+Status after

• Default2  1 (Warning Logo) HTTP

 

I been looking all over the configs but not luck yet.

Any ideas? 

Thank You

[Support]

That means they override a default value. You might have set another password atop of the default one.

[Musarano]

Thank You. I havent been able to locate that default value, that i have no idea where can that be

I did the same to other accounts under extensions,  and that hasnt show to the rest of them.  Only this one in particular..

All using the same dialPlan and same Trunk.

[Musarano]

if i can be provided with a hint, for what to look or where to look?

Will be greatly appreciated.

Scenario:

I did created a new Domain, with same information as the localhost content had.

Once i done with each domain, i deleted the previous one.

I created a defaultxxx new dialplan, and applied to the new Trunk and its account extensions

All other Account/extensions were identical created and modified, but only that one in part is giving me the HTTP Warning.

Should i delete the whole account or renamed?

Thank You

Dalton

[Support]

Your license does say "webRTC support" on it on this page /reg_status.htm right?

[Musarano]

Correct. i have the hosted version.

Additional license information:

Domains: 3/1000, Calls: 0/1000, Alerts: 0/0, Adhoc Recording, CSTA, Lync Connectivity, UHLL support, CRM support, WebRTC support, Barge, Listen, Whisper, Trunk Accounting, Prepaid, Automatic Recording, Fax2Email

[Support]

In that case, can you send us the http login for your PBX. We will test it here.

[Musarano]

i will.

Thank You

[Musarano]

Oh Sorry, i didnt open a new case/post/thread

 

The section that is doing this weird thing is not in Trunks, but in Extensions.

Thats where the warning is poping up.  WEBRTC is working like a Charm.

 

But i never seen this warning before..   I could try to delete it and recreate later tonite.. and get back to you.

unless you think something else is causing this behavior.  There is no signs yet, of secondary effects because of this...  But i will love to get rid of any Flag causes like this one.

 

-M

[Support]

What do you mean the extensions are causing issues? Can you please elaborate or attach screenshots if you can?

[Musarano]

Im reffering to the status of the stations bellow, where all of them were created the same way, and all of them are using the same Trunk and Dial Plan.

No really an idea what could be causing the "Default2 % ^ HTTP" situation of flag.  Can you address me where to look for it?

Or where to look, to find out what could be showing this up?

Thank You!

-M

 

[Musarano]

Hi, and in another kind of matter under same theme.

This line here bellow, should i answer "Yes" to agree with the question? or leave it in NO(Default), to make it like no, do not accept it...

I ask, because, for me is a little confuse 

Don't accept SIP routing changes in dialog

YesNo

 

Thank You

[Musarano]

Humm 

Noticing something here.

By creating another domain name other than localhost,  make the WEBRTC functionality stop from working when hitting Make a Call button?

Because, i did this and what used to work stopped from working..(localhost) and now, neither the newest created domain+webrtc or localhost works.

I had a SSL that pointed to that server where Vodia is running, and there was the localhost domain created.

Do i need to do something else, or need a different kind of SSL Certificate?

Thank You

 

[Musarano]

Sorry, and nevermind. 

For the Previous last post : (Moderator, you can delete this two last posts) prev & this one.

The XIAOMI MI MAX 3, where testing this time, was set to default MI Browser.. Nothing related to VodiaPBX!

Thank You!

[Musarano]

15 hours ago, Musarano said:

Hi, and in another kind of matter under same theme.

This line here bellow, should i answer "Yes" to agree with the question? or leave it in NO(Default), to make it like no, do not accept it...

I ask, because, for me is a little confuse 

Don't accept SIP routing changes in dialog

Yes No

 

Thank You

Morning.. any comments on what would be the implications on this?

I found not much info for this particular item.

 

Thank You

 

[Musarano]

On 7/22/2019 at 5:26 PM, Musarano said:

Im reffering to the status of the stations bellow, where all of them were created the same way, and all of them are using the same Trunk and Dial Plan.

No really an idea what could be causing the "Default2 % ^ HTTP" situation of flag.  Can you address me where to look for it?

Or where to look, to find out what could be showing this up?

Thank You!

-M

 

This has been fixed by, disabling the account and after that, deleted, then re-created the same account.  The warning never showed back again.

Thank You

-M

[Vodia PBX]

The warning sign tells you that the HTTP password is not secure. Just set a good password...

[Musarano]

Thank You.. for the information G-M.

Will keep this information for future use.. 

One question? 

Is it a post/thread where the fail-over discussion is taking place, so i can join it to set this feature and another VodiaPBX instance for redundancy?

Thank You

-M

[Vodia PBX]

12 minutes ago, Musarano said:

Is it a post/thread where the fail-over discussion is taking place, so i can join it to set this feature and another VodiaPBX instance for redundancy?

Just open a new one - does not cost anything 

[Musarano]

Thank You