Toggle sidebar Toggle sidebar

Doorbird & 3CX

Status
Not open for further replies.

fergaloim

Free User
Joined
Jan 12, 2018
Messages
18
Reaction score
2
Trying to enable SIP calling on my Doorbird D101.
Doorbird setup:
  • Doorbird is successfully registered as SIP extension, doorbird sip settings return code 200 so it registers successfully.
  • Allow incoming calls enabled and allowed sip users to relevant 3CX sip caller
  • Schedule for doorbell enabled for 201 extension.

1. 3CX android app (ext 201) calling Doorbird (ext 200), I get "call terminated".
2. Doorbird calling 3CX, it will connect for 2 seconds but then hangs up (I can hear audio very briefly)

Below are the logs for Item 1.

I have seen this post but its locked for replies.
https://www.3cx.com/community/threads/doorbird-d101-works-with-3cx.66365/


Can anyone provide some guidance / experience with Doorbird?


Code: 
06/05/2020 00:05:10 - Leg L:34.1[Extn:201] is terminated: Cause: BYE from PBX
06/05/2020 00:05:10 - Leg L:34.2[Extn:200] is terminated: Cause: 401 Unauthorized/INVITE from IP:5060
06/05/2020 00:05:10 - [CM503020]: Call(C:34): Normal call termination. Call originator: Extn:201. Reason: Terminated
06/05/2020 00:05:10 - [Flow] No office hours set, office hours assumed
06/05/2020 00:05:10 - L:34.1[Extn:201] failed to reach Extn:200, reason Reason Unknown
06/05/2020 00:05:10 - Call to T:Extn:200@[Dev:sip:200@IP:5060;ob] from L:34.1[Extn:201] failed, cause: Cause: 401 Unauthorized/INVITE from IP:5060
06/05/2020 00:05:10 - [CM503003]: Call(C:34): Call to <sip:[email protected]:0> has failed; Cause: 401 Unauthorized/INVITE from IP:5060
06/05/2020 00:05:10 - [CM503025]: Call(C:34): Calling T:Extn:200@[Dev:sip:200@IP:5060;ob] for L:34.1[Extn:201]
06/05/2020 00:05:10 - [CM503027]: Call(C:34): From: Extn:201 (<sip:[email protected]:0>)  to  T:Extn:200@[Dev:sip:200@IP:5060;ob]
06/05/2020 00:05:10 - [CM503004]: Call(C:34): Route 1: from L:34.1[Extn:201] to T:Extn:200@[Dev:sip:200@IP:5060;ob]
06/05/2020 00:05:10 - [Flow] No office hours set, office hours assumed
06/05/2020 00:05:10 - [Flow] Call(C:34): has built target endpoint: Extn:200 for call from L:34.1[Extn:201]
06/05/2020 00:05:10 - [Flow] Target endpoint for 200 is Extn:200
06/05/2020 00:05:10 - [CM503010]: Call(C:34): Making route(s) from Extn:201 to <sip:[email protected]:0/UDP>
06/05/2020 00:05:10 - [CM505001]: Endpoint Extn:201: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: 

[TABLE]
[TR]
[TD][/TD]
[/TR]
[/TABLE]
 
What extension information fields have you data-filled in the device? User, Password, Auth ID...?
 
leejor said:
What extension information fields have you data-filled in the device? User, Password, Auth ID...?
Click to expand...
In 3CX:
Auth_id and user_id need to be the same for a doorbird, set as 200
Password can only be a alphanumeric (no special characters)
First name and email fields also filled

In Doorbird:
SIP Proxy: 3CX FQDN
Sip user: 200
SIP pass: alphanumeric above
Allowed incoming call from another extension [email protected]
Schedule for doorbell set for sip calls from [email protected]
 
Your username and userid should be the same. In the doorbird app select Allow incoming calls and add Allowed sip user (in format [email protected]) otherwise you will not be able to call to the device. keep only ulaw and a-law codec. Also i don't see portnumber <sip:[email protected]:0 ??/UDP>
 
Matspekkie said:
Your username and userid should be the same. In the doorbird app select Allow incoming calls and add Allowed sip user (in format [email protected]) otherwise you will not be able to call to the device. keep only ulaw and a-law codec. Also i don't see portnumber <sip:[email protected]:0 ??/UDP>
Click to expand...
  1. username and userid should be the same - Yes,already said above they are.
  2. Allow incoming calls - done already
  3. Allowed sip user (in format [email protected]) - done already but it is [email protected] (rather than a lan ip)
  4. keep only ulaw and a-law codec - did this but no change
  5. Also i don't see portnumber <sip:[email protected]:0 ??/UDP> - Unsure here. 3CX is a 3CX cloud hosted instance on Amazon, all default settings - unsure why its saying this?
    1. Another line in the log resolves the fqdn.3cx.ie to its actual IP and port. sip:[email protected]:5060

Do you have doorbird working on your own system? If so, what version of 3CX and what type doorbird (and firmware version)?
 
Yes I do have a DoorBird working 101. fwversion 000125. But I have 3CX on premises.
Ringtime is set to? Extension allowed outside lan enabled.
 
Matspekkie said:
Yes I do have a DoorBird working 101. fwversion 000125. But I have 3CX on premises.
Ringtime is set to? Extension allowed outside lan enabled.
Click to expand...
Ok, thanks, on Fw 00124 here, it will roll into 00125 soon I guess.

Ring time set to 20
Disable extension and disable extension use outside lan also unlocked.

Have tried using an SBC also on lan to see if would work, no change.
 
Did you check the firewall (whitelist) on 3cx on for wan ip doorbird??
 
Matspekkie said:
Did you check the firewall (whitelist) on 3cx on for wan ip doorbird??
Click to expand...
Thanks yes, thats ok. Had checked already.

Going through the SBC, I should have no issues with my router firewall.

Firewall check on 3CX instance passes ok except one item

testing 3CX SIP Server... done
  • stopping service... done
  • detecting SIP ALG... not detected
  • testing port 5060... done
  • starting service... done

Possibly I need to install 3CX on lan here.
 
Last edited:
This means your Allowed SIP User does not match what calls in. It wants to see something like 201@ipadress
 
Matspekkie said:
This means your Allowed SIP User does not match what calls in. It wants to see something like 201@ipadress
Click to expand...
Thanks!

Your comment led me to input the ip of the 3cx pbx instead of the 3cx fqdn. Seems doorbird resolves the fqdn to the ip and will reject unless the ip (rather than fqdn) is in the allowed sip users on doorbird.

Lucky my pbx has static ip.


Will raise a ticket with doorbird.

Thanks again for the help.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,948
Messages
589,880
Members
164,841
Latest member
erre
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom