Toggle sidebar Toggle sidebar

Incoming Call rejected doorbell

Status
Not open for further replies.

murno1

Premier Customer
Joined
Jul 16, 2019
Messages
22
Reaction score
0
Hi

we use 3CX Version 15.5.15502 on a virtual machine and about 70 softphones are connected to a sip-trunk. We want o connect an (unsupported) IP doorbell (extension 105). When ringing the bell, another internal extension (150) should be called. But that's where we fail already. Extension 105 has green dot but is UNPROVISIONED under phones.

Extension 105 phone provisioning settings:

Your phones: 3CX Client
Network Interface XXX.XX.XXX.19
SIP Transport: UDP
RTP Mode: Normal
DTMF Mode: RFC2833




Logs:

Code: 
07/16/2019 3:27:27 PM - Terminated from "XXX"<sip:[email protected]:63606>;tag=as27aa5448 to <sip:[email protected]:5060>;tag=f1568751; reason: Rejected



07/16/2019 3:27:27 PM - L:1162.1[Unknown:] Sending: OnSendResp Send 603/INVITE from 0.0.0.0:0 tid=1b183dbf [email protected]:

SIP/2.0 603 Decline

Via: SIP/2.0/UDP 172.17.136.75:63606;branch=z9hG4bK1b183dbf

To: <sip:[email protected]:5060>;tag=f1568751

From: "XXX"<sip:[email protected]:63606>;tag=as27aa5448

Call-ID: [email protected]

CSeq: 103 INVITE

Warning: 499 XXX.XXX "Caller is forbidden"

Content-Length: 0



07/16/2019 3:27:27 PM - SendMsg from <sip:[email protected]:5060>;tag=f1568751 to "XXX"<sip:[email protected]:63606>;tag=as27aa5448



07/16/2019 3:27:27 PM - [CM502001]: Source info: From: "XXX"<sip:[email protected]:63606>;tag=as27aa5448; To: <sip:[email protected]:5060>



07/16/2019 3:27:27 PM - [CM503013]: Call(C:1162): Incoming call rejected, caller is unknown; msg=Invite-IN Recv Req INVITE from 172.17.136.75:63606 tid=1b183dbf [email protected]:

INVITE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 172.17.136.75:63606;branch=z9hG4bK1b183dbf

Max-Forwards: 70

Contact: <sip:[email protected]:63606>

To: <sip:[email protected]:5060>

From: "XXX"<sip:[email protected]:63606>;tag=as27aa5448

Call-ID: [email protected]

CSeq: 103 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Content-Type: application/sdp

Date: Tue, 16 Jul 2019 13:27:27 GMT

Proxy-Authorization: Digest username="105",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:[email protected]:5060",nonce="414d535c133e61bf26:84bcb20fe1982e56e1e482629b278535",response="54139bdf869d0f9187e37a432817ac94"

Supported: replaces

User-Agent: XXX SG

X-Calltype: doorcall

Content-Length: 243



v=0o=root 1376910143 1376910144 IN IP4 172.17.136.75

s=XXX SG

c=IN IP4 172.17.136.75

t=0 0

m=audio 10006 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=maxptime:150

a=sendrecv



07/16/2019 3:27:27 PM - IncomingCall: C:1162 from <sip:[email protected]:63606> to <sip:[email protected]:5060>



07/16/2019 3:27:27 PM - Call from "XXX"<sip:[email protected]:63606>;tag=as27aa5448 to <sip:[email protected]:5060>;tag=f1568751



07/16/2019 3:27:27 PM - [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:

Invite-UNK Recv Req INVITE from 172.17.136.75:63606 tid=0c7aa2cf [email protected]:

INVITE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 172.17.136.75:63606;branch=z9hG4bK0c7aa2cf

Max-Forwards: 70

Contact: <sip:[email protected]:63606>

To: <sip:[email protected]:5060>

From: "XXX" <sip:[email protected]:63606>;tag=as27aa5448

Call-ID: [email protected]

CSeq: 102 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Content-Type: application/sdp

Date: Tue, 16 Jul 2019 13:27:27 GMT

Supported: replaces

User-Agent: XXX SG

X-Calltype: doorcall

Content-Length: 243



v=0

o=root 1376910143 1376910143 IN IP4 172.17.136.75

s=XXX SG

c=IN IP4 172.17.136.75

t=0 0

m=audio 10006 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=maxptime:150

a=sendrecv



07/16/2019 3:27:03 PM - L:1161.1[Extn:150] got Terminated Recv Req CANCEL from XXX.XX.XXX.99:60278 tid=Pj1fd289430cd84a989a9e6d34456ed4ea Call-ID=6ecc83ec5fa44560b56a86eb0450b98c:

CANCEL sip:[email protected];tag3cx=27dfde4fd19e4d6aa562b26367c0079d SIP/2.0

Via: SIP/2.0/TCP XXX.XX.XXX.99:60278;rport=60278;branch=z9hG4bKPj1fd289430cd84a989a9e6d34456ed4ea;alias

Max-Forwards: 70

To: <sip:[email protected];tag3cx=27dfde4fd19e4d6aa562b26367c0079d>

From: "XXX" <sip:[email protected]>;tag=bde53c753a12460eb24dcf90c6a2b7b4

Call-ID: 6ecc83ec5fa44560b56a86eb0450b98c

CSeq: 21782 CANCEL

User-Agent: 3CXPhone for Windows 15.5.12227.5

Content-Length: 0



07/16/2019 3:27:03 PM - Terminated from "XXX"<sip:[email protected]>;tag=bde53c753a12460eb24dcf90c6a2b7b4 to <sip:[email protected];tag3cx=27dfde4fd19e4d6aa562b26367c0079d>;tag=2b470f18; reason: RemoteCancel



07/16/2019 3:27:03 PM - L:1161.1[Extn:150] Sending: OnSendResp Send 487/INVITE from 0.0.0.0:0 tid=Pj1fd289430cd84a989a9e6d34456ed4ea Call-ID=6ecc83ec5fa44560b56a86eb0450b98c:

SIP/2.0 487 Request Terminated

Via: SIP/2.0/TCP XXX.XX.XXX.99:60278;rport=60278;branch=z9hG4bKPj1fd289430cd84a989a9e6d34456ed4ea;alias

To: <sip:[email protected];tag3cx=27dfde4fd19e4d6aa562b26367c0079d>;tag=2b470f18

From: "XXX"<sip:[email protected]>;tag=bde53c753a12460eb24dcf90c6a2b7b4

Call-ID: 6ecc83ec5fa44560b56a86eb0450b98c

CSeq: 21782 INVITE

Content-Length: 0





07/16/2019 3:27:03 PM - SendMsg from <sip:[email protected];tag3cx=27dfde4fd19e4d6aa562b26367c0079d>;tag=2b470f18 to "XXX"<sip:[email protected]>;tag=bde53c753a12460eb24dcf90c6a2b7b4



07/16/2019 3:27:03 PM - L:1161.1[Extn:150] Sending: OnSendResp Send 200/CANCEL from 0.0.0.0:0 tid=Pj1fd289430cd84a989a9e6d34456ed4ea Call-ID=6ecc83ec5fa44560b56a86eb0450b98c:

SIP/2.0 200 OK

Via: SIP/2.0/TCP XXX.XX.XXX.99:60278;rport=60278;branch=z9hG4bKPj1fd289430cd84a989a9e6d34456ed4ea;alias

Contact: <sip:[email protected]:5060>

To: <sip:[email protected];tag3cx=27dfde4fd19e4d6aa562b26367c0079d>;tag=2b470f18

From: "XXX" <sip:[email protected]>;tag=bde53c753a12460eb24dcf90c6a2b7b4

Call-ID: 6ecc83ec5fa44560b56a86eb0450b98c

CSeq: 21782 CANCEL

Content-Length: 0



07/16/2019 3:27:03 PM - SendMsg from <sip:[email protected];tag3cx=27dfde4fd19e4d6aa562b26367c0079d>;tag=2b470f18 to "XXX"<sip:[email protected]>;tag=bde53c753a12460eb24dcf90c6a2b7b4



07/16/2019 3:27:01 PM - L:1161.1[Extn:150] Sending: OnSendResp Send 183/INVITE from 0.0.0.0:0 tid=Pj1fd289430cd84a989a9e6d34456ed4ea Call-ID=6ecc83ec5fa44560b56a86eb0450b98c:

SIP/2.0 183 Session Progress

Via: SIP/2.0/TCP XXX.XX.XXX.99:60278;rport=60278;branch=z9hG4bKPj1fd289430cd84a989a9e6d34456ed4ea;alias

Contact: <sip:[email protected]:5060>

To: <sip:[email protected];tag3cx=27dfde4fd19e4d6aa562b26367c0079d>;tag=2b470f18

From: "XXX"<sip:[email protected]>;tag=bde53c753a12460eb24dcf90c6a2b7b4

Call-ID: 6ecc83ec5fa44560b56a86eb0450b98c

CSeq: 21782 INVITE

Content-Type: application/sdp

Content-Length: 335



v=0

o=3cxPS 526435483648 48637149185 IN IP4 172.17.140.19

s=3cxPS Audio call

c=IN IP4 172.17.140.19

t=0 0

m=audio 7246 RTP/AVP 0 8 9 3 96

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=rtpmap:3 GSM/8000

a=rtpmap:96 telephone-event/8000

a=fmtp:96 0-15

a=sendrecv

m=video 0 RTP/AVP 31

c=IN IP4 127.0.0.1

07/16/2019 3:27:01 PM - SendMsg from <sip:[email protected];tag3cx=27dfde4fd19e4d6aa562b26367c0079d>;tag=2b470f18 to "XXX"<sip:[email protected]>;tag=bde53c753a12460eb24dcf90c6a2b7b4
Any ideas?

Thanks a lot.
 
Last edited by a moderator:
Extension 105 will shown 'Unprovisioned' as you have not used 3CX templates to set it up - this is not an issue as long as you have the correct settings entered in the doorbell.

Can you call ext 105 from a phone, and does it answer ?

On the doorbell, have you setup the unit to dial 150 when the button is pressed ?

What doorbell do you have, someone may have the same model and help you more
 
Unfortunately it doens't answer
 
You've X'd out all the IP's , so I have to assume that they are public IP's, not private. This leads me to believe that the Phones are remote to the server...so, are they behind an SBC, using STUN (with that many sets, I would hope not).

murno1 said:
07/16/2019 3:27:27 PM - [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
Click to expand...
 
murno1 said:
Unfortunately it doens't answer
Click to expand...

This is the issue, you need to resolve this first.

Is the 3CX server hosted in the cloud, and is the doorbell local - if so the unit may need extra settings in terms of stun server etc.

What doorbell is it.
 
Only private IP's. There was a red message which said I should delete private IP's ;)

Doorbell is Siedle SG650. According to manufacturer, it is not meant to be called.
 
I can't see an issue posting private IP's, only public. Most users use the same (limited) choice of private IP's with only slight changes to the subnet, and they are not something usable by a hacker from outside your network. Without seeing the IP's (how the call is routing internally). it is difficult to even guess what's going on.
 
leejor said:
I can't see an issue posting private IP's, only public. Most users use the same (limited) choice of private IP's with only slight changes to the subnet, and they are not something usable by a hacker from outside your network. Without seeing the IP's (how the call is routing internally). it is difficult to even guess what's going on.
Click to expand...

added IPs ;)
 
Are the 3CX server, and the door phone on different subnets? I'm seeing 172.17.140.19:5060 and... INVITE from 172.17.136.75:63606 and Via: SIP/2.0/TCP XXX.XX.XXX.99:60278, whatever the last one is. Try assigning the doorphone an IP on the same subnet as the server.
 
In fact door phone and server are one different subnets. How can this be an issue? I will put both on the same subnet and tell the result
 
I just wonder if 3CX sees the different subset as not being "local".
 
Hi again, sorry for my long absence. I've put door phone and 3cx server both on subnet 172.17.140.X. But still same result as explained above.

Are there further suggestions? I have no idea.

Here are my new logs:

Code: 
08/09/2019 2:19:46 PM - Default best-route IP is determined as 172.17.140.19

08/09/2019 2:19:45 PM - Leg L:9051.1[Unknown:] is terminated: Cause: BYE from PBX

08/09/2019 2:19:45 PM - Terminated from "XXX"<sip:[email protected]:63606>;tag=as3acc9b88 to <sip:[email protected]:5060>;tag=ec3f581f; reason: Rejected

08/09/2019 2:19:45 PM - L:9051.1[Unknown:] Sending: OnSendResp Send 603/INVITE from 0.0.0.0:0 tid=57887db4 [email protected]:



SIP/2.0 603 Decline

Via: SIP/2.0/UDP 172.17.140.75:63606;branch=z9hG4bK57887db4

To: <sip:[email protected]:5060>;tag=ec3f581f

From: "XXX"<sip:[email protected]:63606>;tag=as3acc9b88

Call-ID: [email protected]

CSeq: 103 INVITE

Warning: 499 3CXServerFQDN "Caller is forbidden"

Content-Length: 0



08/09/2019 2:19:45 PM - SendMsg from <sip:[email protected]:5060>;tag=ec3f581f to "XXX"<sip:[email protected]:63606>;tag=as3acc9b88

08/09/2019 2:19:45 PM - OnOffer from "XXX"<sip:[email protected]:63606>;tag=as3acc9b88

08/09/2019 2:19:45 PM - [CM502001]: Source info: From: "XXX"<sip:[email protected]:63606>;tag=as3acc9b88; To: <sip:[email protected]:5060>

08/09/2019 2:19:45 PM - [CM503013]: Call(C:9051): Incoming call rejected, caller is unknown; msg=Invite-IN Recv Req INVITE from 172.17.140.75:63606 tid=57887db4 [email protected]:



INVITE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 172.17.140.75:63606;branch=z9hG4bK57887db4

Max-Forwards: 70

Contact: <sip:[email protected]:63606>

To: <sip:[email protected]:5060>

From: "XXX"<sip:[email protected]:63606>;tag=as3acc9b88

Call-ID: [email protected]

CSeq: 103 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Content-Type: application/sdp

Date: Fri, 09 Aug 2019 12:19:45 GMT

Proxy-Authorization: Digest username="105",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:[email protected]:5060",nonce="414d535c135df5e136:6c7ebb2dfa55d3ade7057c108c8be6ea",response="ebee2805d112314ad09609515f6d937c"

Supported: replaces

User-Agent: Siedle SG

X-Calltype: doorcall

Content-Length: 243



v=0

o=root 1768632834 1768632835 IN IP4 172.17.140.75

s=Siedle SG

c=IN IP4 172.17.140.75

t=0 0

m=audio 10008 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=maxptime:150

a=sendrecv



08/09/2019 2:19:45 PM - Call(C:9051) is terminated

08/09/2019 2:19:45 PM - IncomingCall: C:9051 from <sip:[email protected]:63606> to <sip:[email protected]:5060>

08/09/2019 2:19:45 PM - Added leg L:C:9051.1[No endpoint yet]

08/09/2019 2:19:45 PM - Call from "XXX"<sip:[email protected]:63606>;tag=as3acc9b88 to <sip:[email protected]:5060>;tag=ec3f581f

08/09/2019 2:19:45 PM - [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:



Invite-UNK Recv Req INVITE from 172.17.140.75:63606 tid=539ff8d1 [email protected]:

INVITE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 172.17.140.75:63606;branch=z9hG4bK539ff8d1

Max-Forwards: 70

Contact: <sip:[email protected]:63606>

To: <sip:[email protected]:5060>

From: "XXX" <sip:[email protected]:63606>;tag=as3acc9b88

Call-ID: [email protected]

CSeq: 102 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Content-Type: application/sdp

Date: Fri, 09 Aug 2019 12:19:45 GMT

Supported: replaces

User-Agent: Siedle SG

X-Calltype: doorcall

Content-Length: 243



v=0

o=root 1768632834 1768632834 IN IP4 172.17.140.75

s=Siedle SG

c=IN IP4 172.17.140.75

t=0 0

m=audio 10008 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=maxptime:150

a=sendrecv
 
Last edited by a moderator:
Well, this certainly doesn't look good. Are you able to call any other set from Ext 105 (the door phone)?
Click to expand...
If I use a soft client I can call from 105. But not from the door phone.

Which IP belongs to Ext 105? Any reason the port is not 5060?
Click to expand...
..19 is 3CX Server and ...75 door phone (Ext 105). Good question why port 63606 is used :( settings say port 5060
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,933
Messages
589,810
Members
164,808
Latest member
jsbjsb
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom