0

Issues with private trunk on WAN

Simon Brazeau

April 01, 2019 04:39

None

Follow

I’m having problems configuring a private trunk with my Yeastar S50. I’ve configured the S50 with an online sip provider with 1 phone without problems. Both inbound and outbound calls work perfect.  Now I wanted to add my ISP private trunk but can’t seems to get it working completely.

Private trunk info
Gateway  172.17.4.89
PBX IP  172.17.4.90
Subnet  255.255.255.248 /29

Media 172.17.2.10
SIP 172.17.2.15

So, at this point what I did once the S50 was working fine with my first online SIP, I enabled mode to dual and configured my WAN interface. Next, I added a static route for 172.17.2.0/255.255.255.0 to the WAN port.

The S50 registers with my ISP but when I make a call, my ISP side rejects my invite because the from URI is wrong and contains the IP of the SIP server instead the IP assigned for my PBX system. I’ve included 2 packets provided by my ISP. First one if the one with the wrong info and the second is one from my existing FreePBX system that is working.

 

Any idea why I am not sending my own IP in the From invite?

• Facebook
• Twitter
• LinkedIn

8 comments

• 
  Pixy Tse April 12, 2019 03:20 Official comment

  Issue fixed.

  1. Change the Domain Field of SIP peer trunk to the IP address of WAN IP.
  2. NAT in SIP settings is disabled.
• 0
  
  Riddhe M April 02, 2019 02:23

  how about changing the Domain field in the your trunk to the IP address of WAN port?

• 0
  
  Simon Brazeau April 10, 2019 04:44

  This does not seem to fix anything.

  The only thing that works is I'm setting the "NAT Type" to "external IP address" and using the IP of the PBX WAN and adding my local subnet bellow in the "Local Network Identification".

  Not sure if this correct or if it effects anything else??

• 0
  
  Graham Aker April 10, 2019 05:21

  As the previous description of the issue, the from field for first packet is wrong. It seems that related to the wrong IP 172.17.2.15 in from field. When you use NAT, the IP address may change to WAN. I suppose carrier has restriction of the IP address in from field. You may get the packet with the working setting to compare the difference between the wrong one.

• 0
  
  Simon Brazeau April 10, 2019 16:33

  Sorry I am not really catching what you are trying to tell me. I did do more testing today and it seems that I have to act like I'm NATed at the WAN port so that the FROM contains the correct IP of my PBX. Again i'm not sure why, I've compared other clients with FreePBX system and the NAT was also enabled.

• 0
  
  Kassim Massop May 12, 2021 12:13

  I have an identical issue on the S100 & S300 boxes.

  Setting up NAT did not fix the issue for me either as it still puts the same IP in the "From" & "To" fields.

   

  Did anyone find a real fox for this?

• 0
  
  Simon Brazeau May 12, 2021 12:20

  It has been a while but I think what I had to do is add a route to have it work. Using the IP of the providers trunk I did a ping from the PBX and seen it was going out the wrong port, adding a route to direct it to the WAN port fixed it. 

• 0
  
  Kassim Massop May 12, 2021 12:47

  I did try add a static route but the issue persists.

  I have raised a separate ticket on this matter, the solution in the past was to have Yeastar write a custom firmware to fix this but anytime you change the Public IP of the PBX the issue returns. Not very efficient.