BCM450 sip trunk wants to do Direct Sip only

[Rosesam]

Ok, So I'm using a BCM450(soon to be replaced by a Meridian 1) with sip trunks to a 3CX and * box. Both * and 3cx are not letting the BCM do any external calls save for extensions on the VIOP PBXs. When I look at the logs I get this. in 3cx I've made sure to uncheck the "Enable PCI compliance SSL/SecureSIP Transport and Ciphers" box. I've heard of folks that run this config just fine so I'm not sure what I'm doing.

03/09/2023 9:48:57 PM - [CM503013]: Call(C:50): Incoming call rejected, caller is unknown; msg=Invite-IN Recv Req INVITE from 192.168.1.235:5060 tid=-27e1a3-9bc96655-a623bfe Call-ID=349c28a0-c0a801eb-13c4-55013-27e1a3-6a9538dd-27e1a3:
INVITE sip:EXTERNALPHONE@192.168.1.224;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.235:5060;branch=z9hG4bK-27e1a3-9bc96655-a623bfe
Max-Forwards: 70
Contact: <sip:100@192.168.1.235:5060;transport=udp>
To: <sip:EXTERNALPHONE@192.168.1.224>
From: <sip:100@192.168.1.235>;tag=3485e448-c0a801eb-13c4-55013-27e1a3-3f8576d3-27e1a3
Call-ID: 349c28a0-c0a801eb-13c4-55013-27e1a3-6a9538dd-27e1a3
CSeq: 2 INVITE
Allow: INVITE, INFO, ACK, OPTIONS, CANCEL, BYE, NOTIFY, PRACK, UPDATE, REFER
Content-Type: application/sdp
Proxy-Authorization: Digest username="100",realm="3CXPhoneSystem",nonce="414d535c1a1b39a951:7585fe050b10831bbbcfb421c83d1545",uri="sip:EXTERNALPHONE@192.168.1.224;transport=udp",response="8690771b0224cea4a9a72700ba8a8fcb",algorithm=MD5
Supported: sipvc, x-nortel-sipvc, 100rel, replaces
User-Agent: Nortel Networks BCM VoIP Gateway release_46 version_46.30.0.33
P-Asserted-Identity: <sip:100@192.168.1.235>
x-nt-corr-id: 349c28a0-c0a801eb-13c4-55013-27e1a3-6a9538dd-27e1a3
Content-Length: 267

v=0
o=- 1678420137 1678420137 IN IP4 192.168.1.235
s=-
c=IN IP4 192.168.1.235
t=0 0
m=audio 28006 RTP/AVP 0 18 120 111
c=IN IP4 192.168.1.235
a=fmtp:18 annexb=yes
a=rtpmap:120 telephone-event/8000
a=fmtp:120 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=sendrecv
03/09/2023 9:48:57 PM - Leg L:50.1[Unknown:] is terminated: Cause: BYE from PBX
03/09/2023 9:48:57 PM - Terminated from <sip:100@192.168.1.235>;tag=3485e448-c0a801eb-13c4-55013-27e1a3-3f8576d3-27e1a3 to <sip:EXTERNALPHONE@192.168.1.224>;tag=ee597f0d; reason: Rejected
03/09/2023 9:48:57 PM - L:50.1[Unknown:] Sending: OnSendResp Send 603/INVITE from 0.0.0.0:0 tid=-27e1a3-9bc96655-a623bfe Call-ID=349c28a0-c0a801eb-13c4-55013-27e1a3-6a9538dd-27e1a3:
SIP/2.0 603 Decline
Via: SIP/2.0/UDP 192.168.1.235:5060;branch=z9hG4bK-27e1a3-9bc96655-a623bfe
To: <sip:EXTERNALPHONE@192.168.1.224>;tag=ee597f0d
From: <sip:100@192.168.1.235>;tag=3485e448-c0a801eb-13c4-55013-27e1a3-3f8576d3-27e1a3
Call-ID: 349c28a0-c0a801eb-13c4-55013-27e1a3-6a9538dd-27e1a3
CSeq: 2 INVITE
Warning: 499 CJRS-ADSVR-01.ad.rosesam.local "Caller is forbidden"
Content-Length: 0

03/09/2023 9:48:57 PM - SendMsg from <sip:EXTERNALPHONE@192.168.1.224>;tag=ee597f0d to <sip:100@192.168.1.235>;tag=3485e448-c0a801eb-13c4-55013-27e1a3-3f8576d3-27e1a3
03/09/2023 9:48:57 PM - Call(C:50) is terminated
03/09/2023 9:48:57 PM - IncomingCall: C:50 from <sip:100@192.168.1.235:0/UDP> to <sip:EXTERNALPHONE@192.168.1.224:0/udp>
03/09/2023 9:48:57 PM - Added leg L:C:50.1[No endpoint yet]
03/09/2023 9:48:57 PM - Call from <sip:100@192.168.1.235>;tag=3485e448-c0a801eb-13c4-55013-27e1a3-3f8576d3-27e1a3 to <sip:EXTERNALPHONE@192.168.1.224>;tag=ee597f0d
03/09/2023 9:48:57 PM - [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
Invite-UNK Recv Req INVITE from 192.168.1.235:5060 tid=-27e1a3-9bc965ff-72004860 Call-ID=349c28a0-c0a801eb-13c4-55013-27e1a3-6a9538dd-27e1a3:
INVITE sip:EXTERNALPHONE@192.168.1.224;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.235:5060;branch=z9hG4bK-27e1a3-9bc965ff-72004860
Max-Forwards: 70
Contact: <sip:100@192.168.1.235:5060;transport=udp>
To: <sip:EXTERNALPHONE@192.168.1.224>
From: <sip:100@192.168.1.235>;tag=3485e448-c0a801eb-13c4-55013-27e1a3-3f8576d3-27e1a3
Call-ID: 349c28a0-c0a801eb-13c4-55013-27e1a3-6a9538dd-27e1a3
CSeq: 1 INVITE
Allow: INVITE, INFO, ACK, OPTIONS, CANCEL, BYE, NOTIFY, PRACK, UPDATE, REFER
Content-Type: application/sdp
Supported: sipvc, x-nortel-sipvc, 100rel, replaces
User-Agent: Nortel Networks BCM VoIP Gateway release_46 version_46.30.0.33
P-Asserted-Identity: <sip:100@192.168.1.235>
x-nt-corr-id: 349c28a0-c0a801eb-13c4-55013-27e1a3-6a9538dd-27e1a3
Content-Length: 267

v=0
o=- 1678420137 1678420137 IN IP4 192.168.1.235
s=-
c=IN IP4 192.168.1.235
t=0 0
m=audio 28006 RTP/AVP 0 18 120 111
c=IN IP4 192.168.1.235
a=fmtp:18 annexb=yes
a=rtpmap:120 telephone-event/8000
a=fmtp:120 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=sendrecv

 

[curlycord]

I don't know, sorry, some might, all I know is 3cx does not work with BCM "SIP Trunks" or other 3rd party mobile apps.
I have Yealink on my desk (and in my way) connected to our 3cx system and had preferred to setup a SIP Trunk on my BCM, but that was shot down quickly.

QueBall780 made a nice post that might help

https://www.tek-tips.com/viewthread.cfm?qid=1804158

=----(((((((((()----=

http://www.curlycord.com

Toronto, Canada

Add me to LinkedIN

 

[phonebits]

Generally 3CX doesn't do peer SIP trunking with other PBXs very well. They do not support tie trunks with any other non 3CX system and are increasingly restricting PSTN trunking to their preferred carriers as well. I've only ever encountered a few folks who were able to get a kind-of functional setup going, but never any tight level of integration.

Suggesting support for this type of feature in the 3CX support forum has also gotten a few partner accounts banned. In at least one instance where the CEO was particularly offended at the suggestion their product lacked a feature people might find useful, all licensing for systems associated with the partner account were instantly terminated and the systems shut down. Tread lightly.

 

[Rosesam]

Well... Thats lovely. Might just say screw it and deal with it for a bit while I wait for my M1.. When that gets in I'm just putting some extentions on it into FXO boxes