• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Solved Webmeeting : https://mydomain-uk.3cx.net refused to connect

Status
Not open for further replies.

Premkumar Ekambaram

Joined
Jul 30, 2017
Messages
8
Reaction score
0
Just provisioned Google cloud based 3cx pbx express ... the extension seems to work fine but the web meeting url is throwing above error

Please advise

Prem
 
The service should be back up and running again. Sunday is usually the day on which we perform scheduled updates and maintenance for our WebMeeting service. Soon we plan to have a way to notify users that this is the case.
 
Thanks for your response, still see that i'm unable to launch a webmeeting with video from my client. Is this still down ?

Prem
 
The said maintenance lasted only 15 minutes. The error you're getting must be something else.
Can you please PM me a WebMeeting Link that doesn't work for you?
 
Hi

this issue is now resolved. Now the issue is with new SIP trunk setup.

i have configured SIP trunk using GoTrunk provider. I can now receive calls from PSTN network, but unable to make calls to pstn from 3cx client. Please help

regards
Prem
 
Hello @Premkumar Ekambaram

It is always best to use supported providers that have been tested by us and we know they work. That way we can provide better assistance when an issue occurs.
Having said that, can you call different numbers or is the issue only with PSTN numbers? Also what if you call from an IP phone? Does that work?
Is there an outbound rule in place that matches the number you are dialling?
Did you pass the firewall checker pass?
When you make a call do you see an error in the activity log of the PBX regarding that call? Does it provide a reason why the call failed?
 
Having said that, can you call different numbers or is the issue only with PSTN numbers?
The issue is with all PSTN numbers, no outbound calls is working.

Also what if you call from an IP phone?
Call from IP phone to 3cx client works fine. i.e, inbound calls from both pstn and ip works

Is there an outbound rule in place that matches the number you are dialling?
i tried different outbound rules based on 3cx documentation but nothing worked.
at the moment there is no outbound rules in place

Did you pass the firewall checker?
Yes, the firewall tests seems ok

When you make a call do you see an error in the activity log of the PBX regarding that call? Does it provide a reason why the call failed?
08/01/2017 10:22:52 AM Premkumar Ekambaram (001) +442070001234 Not Answered
08/01/2017 10:10:49 AM Premkumar Ekambaram (001) +442070001234 Not Answered
08/01/2017 10:10:23 AM Premkumar Ekambaram (001) +442070001234 Not Answered
08/01/2017 10:09:39 AM Premkumar Ekambaram (001) +442070001234 Not Answered
08/01/2017 9:53:01 AM Premkumar Ekambaram (001) +442070001234 Not Answered

08/01/2017 12:05:48 PM - There's another STUN server that resolves to the same IP: 151.80.125.93:3478; ignored
08/01/2017 11:45:48 AM - There's another STUN server that resolves to the same IP: 151.80.125.93:3478; ignored
08/01/2017 11:25:48 AM - There's another STUN server that resolves to the same IP: 151.80.125.93:3478; ignored
08/01/2017 11:25:48 AM - Set log verbosity to MaxLevel = 2, Severity mask = 7
08/01/2017 11:25:48 AM - Remove registration: aor=001 contact=sip:[email protected]:5488;rinstance=9886fb61beeaf0c0; id=290
08/01/2017 11:25:48 AM - Removing contact from database: aor=001 contact=sip:[email protected]:5488;rinstance=9886fb61beeaf0c0;total found=1
08/01/2017 11:25:48 AM - Recorded contact <sip:[email protected]:5488> has expired (delta = 0)
08/01/2017 11:25:48 AM - Remove registration: aor=001 contact=sip:[email protected]:50195;transport=TCP;rinstance=1-a8skzcgopydgpgol-.txqjr-adhowpxg;ob; id=286
08/01/2017 11:25:48 AM - Removing contact from database: aor=001 contact=sip:[email protected]:50195;transport=TCP;rinstance=1-a8skzcgopydgpgol-.txqjr-adhowpxg;ob;total found=2
08/01/2017 11:25:48 AM - Ignored non-UDP contact: sip:[email protected]:50195;transport=TCP;rinstance=1-a8skzcgopydgpgol-.txqjr-adhowpxg;ob
08/01/2017 11:25:48 AM - Remove registration: aor=108 contact=sip:[email protected]:5488;rinstance=e6b23a9aac52dcd4; id=151
08/01/2017 11:25:48 AM - Removing contact from database: aor=108 contact=sip:[email protected]:5488;rinstance=e6b23a9aac52dcd4;total found=1
08/01/2017 11:25:48 AM - Recorded contact <sip:[email protected]:5488> has expired (delta = 18446744073709551611)
08/01/2017 11:25:48 AM - Contact record is created; cid = 698535473
08/01/2017 11:25:48 AM - Dev(1549895529):[sip:[email protected]:5488;rinstance=3a126a6bc32b6ad3 / 106]: PBX contact is local IP: <sip:[email protected]:5060>
08/01/2017 11:25:48 AM - Selected source IPv4 127.0.0.1 for destination 127.0.0.1
08/01/2017 11:25:48 AM - Dev(1549895529):[sip:[email protected]:5488;rinstance=3a126a6bc32b6ad3 / 106]: Real source is not known yet, is set to outbound: 127.0.0.1:5488
08/01/2017 11:25:48 AM - Created device Dev(1549895529):[sip:[email protected]:5488;rinstance=3a126a6bc32b6ad3 / 106]: AOR = <sip:[email protected]:5060>
08/01/2017 11:25:48 AM - Update AOR sip:[email protected] with contact [<sip:[email protected]:5488;rinstance=3a126a6bc32b6ad3>]
08/01/2017 11:25:48 AM - Loading Contact records from database
08/01/2017 11:25:48 AM - New list of blocked countries: [001,001242,001246,001264,001268,001284,001340,001345,001441,001473,001649,001664,001670,001671,001684,001758,001767,001784,001787,001809,001829,001849,001868,001869,001876,001939,0020,00211,00212,00213,00216,00218,00220,00221,00222,00223,00224,00225,00226,00227,00228,00229,00230,00231,00232,00233,00234,00235,00236,00237,00238,00239,00240,00241,00242,00243,00244,00245,00246,00247,00248,00249,00250,00251,00252,00253,00254,00255,0025524,00256,00257,00258,00260,00261,00262,00262269,00263,00264,00265,00266,00267,00268,00269,00269639,0027,00290,002908,00291,00297,00298,00299,0030,0031,0032,0033,0034,00350,00351,00352,00353,00354,00355,00356,00357,00358,00359,0036,00370,00371,00372,00373,00374,00375,00376,00377,00378,00380,00381,00382,00385,00386,00387,00389,0039,003906698,0040,0041,00420,00421,00423,0043,00441481,00441534,00441624,0045,0046,0047,004779,0048,0049,00500,00501,00502,00503,00504,00505,00506,00507,00508,00509,0051,0052,0053,0054,0055,0056,0057,0058,00590,00591,00592,00593,00594,00595,00596,00597,00598,005993,005994,005995,005997,005998,005999,0061,006189162,0064,00672,00674,00675,00676,00677,00678,00679,00680,00681,00682,00683,00685,00686,00687,00688,00689,00690,00691,00692,00699,007,00870,00871,00872,00873,00874,00875,00876,00877,00878,00879,00881,00882,00883,0090,0090392,00979]
08/01/2017 11:25:48 AM - Issue: [Pres:10000; act=Closed;1;23]
08/01/2017 11:25:48 AM - Failed to add outbound CID reformating rule for DN:10000: <Rules />
 
Please someone help me with this issue ....
 
08/02/2017 1:06:45 PM - Call to T:Line:10000>>902070001234@[Dev:sip:[email protected]:5060] from L:23.1[Extn:001] failed, cause: Cause: 407 Proxy Authentication Required/INVITE from 109.233.115.107:5060
08/02/2017 1:06:45 PM - [CM503003]: Call(C:23): Call to <sip:[email protected]:5060> has failed; Cause: 407 Proxy Authentication Required/INVITE from 109.233.115.107:5060
08/02/2017 1:06:44 PM - Call to T:Line:10000>>902070001234@[Dev:sip:[email protected]:5060] from L:23.1[Extn:001] failed, cause: Cause: 407 Proxy Authentication Required/INVITE from 109.233.115.107:5060

thanks the error msg i'm getting ..
 
Without a valid outbound rule calls will never work. I would recommend creating a very generic outbound rule to make sure the issue is not there. Just add the extension you are using to call or the group the extension is a part of.
Now since incoming calls are working i would assume the trunk is registered correctly.

08/02/2017 1:06:44 PM - Call to T:Line:10000>>902070001234@[Dev:sip:[email protected]:5060] from L:23.1[Extn:001] failed, cause: Cause: 407 Proxy Authentication Required/INVITE from 109.233.115.107:5060

Is the IP 109.233.115.107 the ip of your provider? If so i would recommend calling them and asking why they are sending this error. Since this is a not supported provider we have no way of knowing their correct settings. Perhaps you are sending the wrong information in certain SIP fields and they do not accept the calls. They will need to specify these settings to you so you can make the appropriate adjustments.
 
thanks for this, as mentioned i did amend the outbound rule and it worked
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,626
Messages
748,910
Members
144,738
Latest member
Ghisl1
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.