Solved planet ip pbx and 3cx

[chanklish]

hello awesome people
i have 3 planet appliance ip pbx ( 1900 ) that are connected together with something called site-to-site in the planet config
i replaced one of these pbx with 3cx and it is working normally , but now i want to connect it to the other two pbx
i created a trunk and inbound/outbound rules on the 3cx but i am getting this error
192.168.120.251 is the planet ip
192.168.140.3 is the 3cx

Search ...
03/18/2019 3:09:02 PM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.120.251:5060 tid=5bae3d26 [email protected]:
REGISTER sip:192.168.140.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.120.251:5060;branch=z9hG4bK5bae3d26
Max-Forwards: 70
Contact: <sip:[email protected]>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=as081b893c
Call-ID: [email protected]
CSeq: 103 REGISTER
Expires: 360
Proxy-Authorization: Digest username="6666",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:192.168.140.3",nonce="414d535c12a0377e34:657275b36210b7baa15c3c5e7922fa8c",response="7fc1409255d274737ee351511c8de418",opaque=""
User-Agent: PBX
Event: registration
Content-Length: 0

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

 

[leejor]

How have you set up the trunk in 3CX, as a Bridge, so the other PBX can register? Or...is the other PBX able to act as a SIP server? Did you read through this?

https://www.3cx.com/docs/

 

[chanklish]

How have you set up the trunk in 3CX, as a Bridge, so the other PBX can register? Or...is the other PBX able to act as a SIP server? Did you read through this?

https://www.3cx.com/docs/

I added a generic trunk and inbound and outbound rules on the 3cx
The trunk is showing green and up

The other ip pbx is a sip server

I used this as a template https://support.yeastar.com/hc/en-u...nd-Yeastar-S-Series-VoIP-PBX?mobile_site=true

 

[leejor]

Is that Planet PBX designed to be interconnected with "other" PBXs (3CX) using the setup page you posted, or is there something proprietary going on that may be preventing 3CX from registering? Have you tried using Wireshark?

 

[chanklish]

Is that Planet PBX designed to be interconnected with "other" PBXs (3CX) using the setup page you posted, or is there something proprietary going on that may be preventing 3CX from registering? Have you tried using Wireshark?

i do not know .. the planet ip pbx has trunks, sip , etc .. a regular ip pbx
the planet phones works perfectly with 3cx and their planet pbx

what would wireshark help with ? i already posted the error

 

[JohnS_3CX]

From your error it seems like the Planet IPX-1900 is rejecting the register invite from 3CX because the credentials don't match

 

[chanklish]

planet sent me a powerpoint how to connect 2 planet sip server , i will try to adapt it to 3cx and test

 

[JohnS_3CX]

I think the problem is that the Planet UAS does not accept 3CX as a UAC and I don't know how you can configure that or if it can work at all.

This can be solved with 3CX bridges if you replace all 3 systems with 3CX PBX
https://www.3cx.com/docs/manual/connecting-pbx-bridges/

This allows 3CX systems to bridge between themselves and you can have extensions communication and presence across the bridges, you can use the SIP trunks of the other bridges for outgoing calls if you wish to save on call costs with a cheaper route, or as redundancy in case your main route goes down.

 

[chanklish]

i contacted planet and got from them how to connect to sip servers
i am now able to call the 3cx from the planet , but not the way around
in the planet i added a dialing rule : i call 8 + any extension in the 3cx and the call works

in the 3cx i added an outbound dialing rule ( but im sure something is wrong - i added it in the pictures ) to dial 7 + extension but it wont pass

i created extensions on planet ( 299 ) and on the 3cx (499) for authentication

 

[JohnS_3CX]

In your 3CX "Socimex" outbound rule, try to strip one digit so when you dial say extension 7100, it will only ask the Planet to call extension 100.

Now it's asking to to call extension "7100" instead of extension "100" and that would be a reason to cause it to fail

 

[chanklish]

In your 3CX "Socimex" outbound rule, try to strip one digit so when you dial say extension 7100, it will only ask the Planet to call extension 100.

Now it's asking to to call extension "7100" instead of extension "100" and that would be a reason to cause it to fail

in the planet i dial 8 + extension
now after stripping 1 digit in 3cx i should still dial 7+extension true ?!

 

[JohnS_3CX]

yes correct

 

[chanklish]

yes correct

yes correct

it did not work
i can see these errors

Call or Registration to 203@(Ln.10000@socimex) has failed. 192.168.120.251 replied: 403 Forbidden; from IP:192.168.120.251:5060

03/22/2019 3:43:23 PM - Call to T:Line:10000>>203@[Dev:sip:[email protected]:5060] from L:164.1[Extn:400] failed, cause: Cause: 403 Forbidden/INVITE from 192.168.120.251:5060

03/22/2019 3:43:23 PM - [CM503003]: Call(C:164): Call to <sip:[email protected]:5060> has failed; Cause: 403 Forbidden/INVITE from 192.168.120.251:5060

here i am trying to call extension 203 in the planet pbx

 

[JohnS_3CX]

it looks from the invite that 3CX tried to contact 203 at 192.168.120.251 (planet)

The call reached Planet normally, but it rejected it with a 403 (I understand your request but i reject it)

Check that the rules on the Planet allow calls coming in from 3CX

 

[chanklish]

it looks from the invite that 3CX tried to contact 203 at 192.168.120.251 (planet)

The call reached Planet normally, but it rejected it with a 403 (I understand your request but i reject it)

Check that the rules on Planet allow calls coming in from 3CX

the
but the trunk is registered successfully in the 3cx
firewall off in both - i dont know what to check

 

[JohnS_3CX]

You need to see why Planet says no when 3CX calls it.

Maybe in the Planet logs?

 

[chanklish]

i had to add a site to site in the planet for it to work and use the pass of the 3cx extension
i works now

 

[JohnS_3CX]

I'm glad it was resolved, thanks for updating the thread