Use Brekeke as SBC

Discuss any topic about Brekeke SIP Server.

Moderator: Brekeke Support Team

Post Reply
zhu.yin
Posts: 2
Joined: Tue Jul 02, 2013 7:36 pm

Use Brekeke as SBC

Post by zhu.yin »

1. Brekeke Product Name and Version:
Brekeke SIP Server 3.1.8.2/348.2

2. Java version:
Java 7 Update 25

3. OS type and the version:
Windows 2008 R2 SP1

4. UA (phone), gateway or other hardware/software involved:
LAN: Lync 2013; WAN: SIP Provider

5. Your problem:
The Brekeke SIP Server in this scenario is used as a simple NAT. None of UA is registered in the BSS. The BSS has two interfaces. One LAN interface 192.168.0.2 and one Internet interface 64.x.x.29. Lync 2013 (192.168.0.11) is configured in the LAN to allow Lync client to registered. A public SIP server (64.x.x.39) is configured to route the outbound calls from BSS.

Lync server communicate with BSS using SIP over TCP via LAN interface. Lync Server port 5068, Brekeke port 5060. BSS communicate with SIP server using SIP over UDP via Internet interface. BSS port 5060, SIP server port 5060.

When a call from Lync is routed to BSS, BSS receive the call from LAN interface and route the call to SIP server using Internet interface. The routing is fine. The SIP server prompts some IVR (eg. Balance, etc). After that, SIP server send an INVITE (reINVITE) but Brekeke response 503 Service Unavailable and disconnect the call session between BSS and SIP server. But the call between BSS and Lync is not disconnected.

May I know why BSS response 503 for the reINVITE? I tried to turn on and off the b2b mode, authentication INVITE is off. Dial Plan from Lync to BSS is as follow

Dial Plan: Lync to SIP Trunk

Matching Patterns
$addr = 192.168.0.11
$request = ^INVITE
To = sip:(.+)@
$registered = false

Deploy Patterns
$transport = udp
To = sip:%1@64.x.x.39:5060
$auth = false
hope
Posts: 862
Joined: Tue Jan 15, 2008 4:08 pm

Post by hope »

zhu.yin
Posts: 2
Joined: Tue Jul 02, 2013 7:36 pm

Post by zhu.yin »

Thank you very much. It woks now. :D
james
Posts: 501
Joined: Mon Dec 10, 2007 12:56 pm

Post by james »

zhu,

In your case, you need to have &net.sip.transport.follow.request = true in your DialPlan rule.
Post Reply