| Author |
Message |
evzky
Brekeke Junior Member
Joined: 21 Feb 2019
Posts: 7
Location: south africa
|
 Posted: Tue Feb 26, 2019 11:29 pm Post subject: Infinite Loop |
 |
|
1. Brekeke Product Name and Version: Brekeke SIP Server 3.9.1.3/510
2. Java version: java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
3. OS type and the version: 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019-02-02) x86_64 GNU/Linux
4. UA (phone), gateway or other hardware/software involved: FreeSBC, standard yealink voip phone
5. Your problem: Hi All, I'm currently having an issue with inbound calls whereby when we pass the call from our Gateway(an SBC) through to the SIP proxy, it bounces it back gateway and causes an infinite loop. We forward register through our gateway, the calls comes through the gateway to the SIP proxy and the SIP proxy is supposed to pass it back to registered user. But it seems like the SIP proxy does not know how to get back to registered user and it passes it back and forth between the SBC and the proxy.
What I've noticed is that the UAC and the UAS are coming from the same IP which is the LAN IP of the of the SBC where the call is forwarded from. If I register direct to the SIP proxy, it works fine.
Is there some manipulation I need to do in the dialplan perhaps? |
|
| Back to top |
|
Tata
Brekeke Master Guru
Joined: 27 Jan 2008
Posts: 223
|
| Posted: Thu Feb 28, 2019 10:27 am Post subject: |
|
|
Can you see registered users at [Registered Clients] page?
And Contact URI and Source IP Address are valid?
Also let you paste your DialPlan rules here. |
|
| Back to top |
|
evzky
Brekeke Junior Member
Joined: 21 Feb 2019
Posts: 7
Location: south africa
|
| Posted: Thu Feb 28, 2019 11:39 pm Post subject: |
|
|
Hi Tata,
Yes we can and the UA is registered on registered clients page and on my SIP application. The 12345678 is just the number I'm dialing to(the registered user).
First rule:
| Matching Patterns | $request = ^INVITE
To = sip:12345678@
| | Deploy Patterns | To = sip:12345678@
|
Second rule:
| Matching Patterns | $request = ^INVITE
| | Deploy Patterns | $auth = false
|
Contact URI:
sip:12345678-12345678-AlIaS-A13693E7C5BF39--@1.2.3.4:5060
(1.2.3.4:5060)
The contact URI is a remapped contact from the the SBC which is why it has the long string afterwards. The 1.2.3.4 IP is our SBC where the registration is coming from. 12345678 is the registered user. |
|
| Back to top |
|
Tata
Brekeke Master Guru
Joined: 27 Jan 2008
Posts: 223
|
| Posted: Fri Mar 01, 2019 7:04 pm Post subject: |
|
|
evzky...
Because registered Contact URI points the SBC's IP address,
INVITE should be forwarded back to there..
Why does the SBC send it back to the SIP Server??
Do you have any other DialPlan rules?
Let you check the DialPlan history page to see which DialPlan rule is used. |
|
| Back to top |
|
evzky
Brekeke Junior Member
Joined: 21 Feb 2019
Posts: 7
Location: south africa
|
| Posted: Sun Mar 03, 2019 11:20 pm Post subject: |
|
|
Hi Tata,
Yes, the call is being forwarded back to the SBC to the remapped user, but for some reason the call gets passed back to the Brekeke Server.
Rule registered=sip:12345678(sip:12345678-12345678-AlIaS-A13693E7C5836E--@1.2.3.4:5060/UDP) & tsbc_inbound_calls
12345678 = registered user and 1.2.3.4 is the SBC's ip.
The long string is how the SBC remaps the user. |
|
| Back to top |
|
Tata
Brekeke Master Guru
Joined: 27 Jan 2008
Posts: 223
|
| Posted: Wed Mar 06, 2019 1:17 pm Post subject: |
|
|
What does the rule "tsbc_inbound_calls" do?
Are you using B2B-UA mode at Brekeke SIP Server? If so, let you disable it because the SBC might think SIP Server is a UA.
Also check the outgoing packet at DialPlan history to see whether the request URI and To-URI are acceptable at the SBC. |
|
| Back to top |
|
|
