1. Brekeke Product Name and Version: Brekeke SIP Server Version 3.8.3.0
2. Java version: Latest version
3. OS type and the version: Windows 10 Pro
4. UA (phone), gateway or other hardware/software involved: Grandstream SIP device - Model HT503
5. Your problem:
I am trying to send an inbound call from my gateway to BSS using UDP 5060 and then out to my customers Grandstream device using TCP 5060 but for some reason the Brekeke SIP server is rejecting the call with a SIP 603 Declined.
Below is the dial plan that I used.
Matching Patterns
$addr = xxx.xxx.xxx.xxx
$request = ^INVITE
To = sip:(011XXXXXXXXXXX)@
$transport = ^UDP
Deploy Patterns
$transport = TCP
To = sip:%1@yyy.yyy.yyy.yyy
$target = zzz.zzz.zzz.zzz
xxx.xxx.xxx.xxx is my gateway's public IP address
yyy.yyy.yyy.yyy is the public IP address of my BSS server
zzz.zzz.zzz.zzz is the public IP address of my customers gateway.
I am not requiring any SIP registration from the customer on this setup. (I am using IP authentication method based on the IP address assigned to the BSS server)
If I use UDP 5060 on my customers gateway and remove the $transport = TCP statement from the deploy Pattern, I see in Wireshark that my BSS server sends the call out to my customers gateway and the call completes.
If I configure my customers gateway using TCP 5060 and add statement $transport = TCP statement to the deploy Pattern, I never see the BSS server send the inbound call out to my customers gateway. The call is just rejected by the BSS server. I confirmed that TCP is ON under Configuartion / SIP.
Any help on this would be appreciated.
Outbound TCP 5060 to UDP 5060 calls via the BSS server works with no issues.
Inbound call issue - UDP to TCP transport conversion issue
Moderator: Brekeke Support Team
- Check whether [Status]->[SIP Server] page ->[transport] indicates "TCP"
- Check the result phrase at [Logs]->[Session Logs] -> click a date
- Check there is no firewall which blocks the TCP port 5060 at zzz.zzz.zzz.zzz.
- Check if zzz.zzz.zzz.zzz is a router the port-forwarding TCP 5060 is configured to the device.
- Check the result phrase at [Logs]->[Session Logs] -> click a date
- Check there is no firewall which blocks the TCP port 5060 at zzz.zzz.zzz.zzz.
- Check if zzz.zzz.zzz.zzz is a router the port-forwarding TCP 5060 is configured to the device.