0

Yeastar Route Inbound DID to 3CX

David Rocky

March 14, 2018 11:17

None

Follow

We have been provided with a SIP trunk by our ISP. The trunk has DIDs enabled.  

I have been unable to route the DID to 3CX. I followed the following guide for connecting 3CX to yeastar MyPBX: https://support.yeastar.com/hc/en-us/articles/218054487-How-to-Connect-MyPBX-to-3CX

Outbound calls are working fine but the issue comes when I test inbound calls using a DID.

I have configured my Outbound and Inbound rules as shown below.

Outbound rule:

Inbound rule:

However when I test an inbound call the call is dropped. I did a capture and opened it in wireshark and I saw that the request is getting a 603 Declined response.

The DID works fine when I put in an extension on the extension field but it is not routing to 3CX. A wireshark trace on the 3CX server shows that the call is not reaching 3CX. Can someone assist us with this error.

• Facebook
• Twitter
• LinkedIn

8 comments

• 0
  
  Larry Neblett March 15, 2018 13:27

   

  The first thing to do is to confirm that the SIP Trunk to the provider is set correctly on the S20 and that calls can be made an received by the S20 with no issues. 

  If the above is OK, then it assumed that you created peer trunks between the S20 and 3CX and that you also created rules and have tested inter-PBX calling both in and out from one PBX to the other and vice versa. This merely confirms that the connectivity between the two is fine, which I assume to be the case given that you indicated that you could call out, but you did not mention from which system the outbound calls were made nor that you were able to call from an S20 extension to a 3CX extension. 

  You took a wireshark and indicated that you see a 603 decline, but is the decline coming from 3CX?

  My guess is that you need to take a capture and then look at the INVITE being sent by the S20 to 3CX and look at the SIP to Address User Part. Then, in 3CX, you should look at the Trunk settings and compare the DID settings and source DID to see if they match with what is in the User Part. You must have call source identification set on the 3CX side.  

  It may also be helpful to know the 3CX edition and version and if paid or free. 

• 0
  
  David Rocky March 16, 2018 08:39

  Thanks for your response.

  We are using the ProVersion of 3CX and calls between extensions on both PBXs are working fine.

  The Yeastar PBX is a MyPBX-Standard V4  not an S20. The SIP trunk is on the MyPBX. I can make outbound calls from 3CX via that SIP trunk.

  After observing the Wireshark trace again I found that the MyPBX is the one that is dropping the call.

  I think I may have found the cause but I am not sure. The PBX log from the Yeastar MyBPX shows the following:

  

  The DID provided by ISP includes the country code for our country so it starts with a '+'. The wireshark trace also shows that the DID is arriving correctly. Could it be that MyPBX box that we have does not support DIDs that start with '+'?

• 0
  
  Larry Neblett March 16, 2018 11:36

  Well, you indicated that you were able to direct calls to an extension with the DID, so I assume it does in that regard. I assume you could always "strip" the + using the rule and test again.

• 0
  
  David Rocky March 16, 2018 18:44

  The default inbound rule did not have a DID. When I enable the DID inbound calls no longer work.

• 0
  
  Larry Neblett March 16, 2018 20:23

  So when you indicate inbound rule, I take that to mean the inbound rule coming from the provider to the MyPBX?

• 0
  
  David Rocky March 16, 2018 20:47

  Yes that's what I'm referring to.

• 0
  
  Larry Neblett March 18, 2018 13:26

  Maybe this will help. 

  https://support.yeastar.com/hc/en-us/articles/115011732268-How-to-Remove-Prefix-for-Incoming-Caller-ID

   

  I am a little surprised by the date of the article as certainly e.164 has been around for some time now. I suggest you do a backup of the system before hand so that if a mistake is made, you can restore and at least be where you were..... as it may be problematic to examine and then see the mistake to correct. 

• 0
  
  David Rocky March 18, 2018 15:24

  Thanks for this I will test it tomorrow and come with the feedback.