SIP Trunk is not getting registered

[Ameeralitp]

Dear team,
Please refer attached design -- i have two locations both are connected over IPSEC VPN.
Local A is having 3CX On-Premise, and Location2 i have SIP Trunk Connected (to the LAN2 port of Fortigate Firewall).
im unable to register the SIP Trunk (Etisalat UAE) to the 3CX Server. im able to ping 192.168.3.1 from 3CX Server on location A (which is the SIP Gateway local address )
all subnets are pinging back and forth. but unable to get the SIP Trunk registered.
any help in this matter will be highly appreciated
Regards,
Ameer Ali

 

[OlegR_3CX]

Hi Ameer Ali.
Firstly you need to identify where the issue is, if it's a networking/communication or a settings of the trunk etc. To start, you will need to monitor and run the Wireshark capture on the PBX and see if the Phonesystem is sending the register request to the IP of the trunk, if it does, then the trunk must reply something back, you should see this event it in the same capture.
If you don't see anything arriving back to the NIC of the OS where the Phonesystem is installed, then you know it is a network and then you will examine each node from where the packet passes and if it's blocked in a way.

 

[Ameeralitp]

Dear team,
Please refer attached design -- i have two locations both are connected over IPSEC VPN.
Local A is having 3CX On-Premise, and Location2 i have SIP Trunk Connected (to the LAN2 port of Fortigate Firewall).
im unable to register the SIP Trunk (Etisalat UAE) to the 3CX Server. im able to ping 192.168.3.1 from 3CX Server on location A (which is the SIP Gateway local address )
all subnets are pinging back and forth. but unable to get the SIP Trunk registered.
any help in this matter will be highly appreciated
Regards,
Ameer Ali

Thanks for responding olegR,
Please find below the capture results.
No. Time Source Destination Protocol Length Info
1164 18.041976 192.168.1.254 192.168.3.1 SIP/SDP 949 Request: INVITE sip:[email protected]:5060 |

Frame 1164: 949 bytes on wire (7592 bits), 949 bytes captured (7592 bits) on interface \Device\NPF_{7BE988B9-C76D-4EA4-B02D-662B3276BE12}, id 0
Ethernet II, Src: Dell_98:9b:58 (00:be:43:98:9b:58), Dst: Fortinet_62:c8:bf (80:80:2c:62:c8:bf)
Internet Protocol Version 4, Src: 192.168.1.254, Dst: 192.168.3.1
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (INVITE)

No. Time Source Destination Protocol Length Info
1226 18.134520 192.168.1.254 192.168.3.1 SIP 360 Request: ACK sip:[email protected]:5060 |

Frame 1226: 360 bytes on wire (2880 bits), 360 bytes captured (2880 bits) on interface \Device\NPF_{7BE988B9-C76D-4EA4-B02D-662B3276BE12}, id 0
Ethernet II, Src: Dell_98:9b:58 (00:be:43:98:9b:58), Dst: Fortinet_62:c8:bf (80:80:2c:62:c8:bf)
Internet Protocol Version 4, Src: 192.168.1.254, Dst: 192.168.3.1
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (ACK)

No. Time Source Destination Protocol Length Info
1572 23.106789 192.168.1.254 192.168.3.1 SIP/SDP 952 Request: INVITE sip:[email protected]:5060 |

Frame 1572: 952 bytes on wire (7616 bits), 952 bytes captured (7616 bits) on interface \Device\NPF_{7BE988B9-C76D-4EA4-B02D-662B3276BE12}, id 0
Ethernet II, Src: Dell_98:9b:58 (00:be:43:98:9b:58), Dst: Fortinet_62:c8:bf (80:80:2c:62:c8:bf)
Internet Protocol Version 4, Src: 192.168.1.254, Dst: 192.168.3.1
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (INVITE)

No. Time Source Destination Protocol Length Info
1588 23.224009 192.168.1.254 192.168.3.1 SIP 362 Request: ACK sip:[email protected]:5060 |

Frame 1588: 362 bytes on wire (2896 bits), 362 bytes captured (2896 bits) on interface \Device\NPF_{7BE988B9-C76D-4EA4-B02D-662B3276BE12}, id 0
Ethernet II, Src: Dell_98:9b:58 (00:be:43:98:9b:58), Dst: Fortinet_62:c8:bf (80:80:2c:62:c8:bf)
Internet Protocol Version 4, Src: 192.168.1.254, Dst: 192.168.3.1
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (ACK)

 

[OlegR_3CX]

Does it mean that the other side replies to the PBX invite?
You can also see this with your SIP trunk provider.

 

[Ameeralitp]

Does it mean that the other side replies to the PBX invite?
You can also see this with your SIP trunk provider.

Dear OlegR_3CX,
i spoke with the trunk provider, they are saying that, SIP trunk will accept the SIP invite only from the IP Address they mentioned. which is as per my design 192.168.3.254.
so, how do i change the header to send the request as the ip address 192.168.3.254

 

[OlegR_3CX]

In the trunk settings >> Option tab >> you can see the option:
"Select which IP to use in 'Contact' (SIP) and 'Connection'(SDP) fields"
and try to modify it, to see if it makes a difference.