1. Brekeke Product Name and Version:Brekeke SIP Server , Version 2.1.6.6 Standard
2. Java version: Java Verion 7 Update 10(Build 1.6.0_10-b33)
3. OS type and the version:Windows Server 2003 R2, Standard Edition Service pack 2
4. UA (phone), gateway or other hardware/software involved:
Lancom 1783VA
5. Your problem:
Calls from Lancom to Brekeke SIP-server disconnects after 30 seconds.
SIP-trace between Brekeke and Lancom shows:
Options-> 100 trying -> Invite -> 100 Trying -> 183 Session Progress -> 180 ringing -> 200 OK -> ACK.
The last ACK message is sent from Lancom to Brekeke, but Brekeke never forwards the ACK message to next device.
The SIP-sessions last perfectly for 30 seconds with sound both ways, before it disconnect. Call log in Brekeke Show 00:00 seconds.
This is tested with other brands than Lancom, and it then works OK.
Logs from: C:\Program Files\Brekeke\proxy\webapps\proxy\WEB-INF\work\sv\log\2017\11
Exception: java.net.UnknownHostException: SIP
java.net.Inet4AddressImpl.lookupAllHostAddr (null:-2)
java.net.InetAddress$1.lookupAllHostAddr (null:-1)
java.net.InetAddress.getAddressFromNameService (null:-1)
java.net.InetAddress.getAllByName0 (null:-1)
java.net.InetAddress.getAllByName (null:-1)
java.net.InetAddress.getAllByName (null:-1)
java.net.InetAddress.getByName (null:-1)
com.brekeke.net.AddressCommon.getByName (null:-1)
com.brekeke.net.sip.SIPaddrPort.set (null:-1)
com.brekeke.net.sip.SIPaddrPort.<init> (null:-1)
com.brekeke.net.sip.SIPaddrPort.toAddrPort (null:-1)
com.brekeke.net.sip.SIPpacket.analyzeRouteAddress (null:-1)
com.brekeke.net.sip.sv.SIPex.runImple (null:-1)
com.brekeke.thread.ThreadCommon.run (null:-1)
Exception: java.net.UnknownHostException: SIP
java.net.InetAddress.getAllByName0 (null:-1)
java.net.InetAddress.getAllByName (null:-1)
java.net.InetAddress.getAllByName (null:-1)
java.net.InetAddress.getByName (null:-1)
com.brekeke.net.AddressCommon.getByName (null:-1)
com.brekeke.net.sip.SIPaddrPort.set (null:-1)
com.brekeke.net.sip.SIPaddrPort.<init> (null:-1)
com.brekeke.net.sip.SIPaddrPort.toAddrPort (null:-1)
com.brekeke.net.sip.SIPpacket.analyzeRouteAddress (null:-1)
com.brekeke.net.sip.sv.SIPex.runImple (null:-1)
com.brekeke.thread.ThreadCommon.run (null:-1)
Exception: java.net.UnknownHostException: SIP
java.net.Inet4AddressImpl.lookupAllHostAddr (null:-2)
java.net.InetAddress$1.lookupAllHostAddr (null:-1)
java.net.InetAddress.getAddressFromNameService (null:-1)
java.net.InetAddress.getAllByName0 (null:-1)
java.net.InetAddress.getAllByName (null:-1)
java.net.InetAddress.getAllByName (null:-1)
java.net.InetAddress.getByName (null:-1)
com.brekeke.net.AddressCommon.getByName (null:-1)
com.brekeke.net.sip.SIPaddrPort.set (null:-1)
com.brekeke.net.sip.SIPaddrPort.<init> (null:-1)
com.brekeke.net.sip.SIPaddrPort.toAddrPort (null:-1)
com.brekeke.net.sip.SIPpacket.analyzeRouteAddress (null:-1)
com.brekeke.net.sip.sv.SIPex.runImple (null:-1)
com.brekeke.thread.ThreadCommon.run (null:-1)
Brekeke do not accept ACK message from Lancom
Moderator: Brekeke Support Team
It seems ACK is not SIP-compliant packet. Can you paste the ACK packet here?
Also I recommend you to use the latest version of Brekeke SIP Server because the ver 2.1.6.6 is super old.. (It was related almost 10 years ago..) The latest version is 3.7.7.8.
http://wiki.brekeke.com/wiki/BSS_History
Also I recommend you to use the latest version of Brekeke SIP Server because the ver 2.1.6.6 is super old.. (It was related almost 10 years ago..) The latest version is 3.7.7.8.
http://wiki.brekeke.com/wiki/BSS_History
Hi, thanks for fast reply.
Yes, I know it is old. Will be replaced sometime soon.
Please find summary message, and ACK below. I did replace IP and phone numbers with fake ones.
SIP-trace is taken from Host that Brekeke is installed on.
Brekeke: 192.168.16.18
Lancom: 200.100.50.5
Summary:
N9 8!E:o
!K
!ACK sip:55552222@192.168.16.18:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 200.100.50.5.5:5060;branch=z9hG4bK-50e04aac-c996dadf;rport
Route: <SIP:192.168.16.18:5060;lr>
From: "A1"<sip:22223333@192.168.16.18>;tag=-806073797--2107693741
To: <sip:55552222@192.168.16.18;user=phone>;tag=2378483377
Call-ID: 1273912400@00a0572ebfbb
CSeq: 100 ACK
Max-Forwards: 70
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0147 / 15.11.2017
Content-Length: 0
ACK message:
Session Initiation Protocol (ACK)
Request-Line: ACK sip:55552222@192.168.16.18:5060;transport=udp SIP/2.0
Method: ACK
Request-URI: sip:55552222@192.168.16.18:5060;transport=udp
Request-URI User Part: 55552222
Request-URI Host Part: 192.168.16.18
Request-URI Host Port: 5060
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP 200.100.50.5:5060;branch=z9hG4bK-50e04aac-c996dadf;rport
Transport: UDP
Sent-by Address: 200.100.50.5
Sent-by port: 5060
Branch: z9hG4bK-50e04aac-c996dadf
RPort: rport
Route: <SIP:192.168.16.18:5060;lr>
From: "A1"<sip:22223333@192.168.16.18>;tag=-806073797--2107693741
SIP Display info: "A1"
SIP from address: sip:22223333@192.168.16.18
SIP from address User Part: 22223333
SIP from address Host Part: 192.168.16.18
SIP from tag: -806073797--2107693741
To: <sip:55552222@192.168.16.18;user=phone>;tag=2378483377
SIP to address: sip:55552222@192.168.16.18;user=phone
SIP to address User Part: 55552222
SIP to address Host Part: 192.168.16.18
SIP To URI parameter: user=phone
SIP to tag: 2378483377
Call-ID: 1273912400@00a0572ebfbb
CSeq: 100 ACK
Sequence Number: 100
Method: ACK
Max-Forwards: 70
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0147 / 15.11.2017
Content-Length: 0
Yes, I know it is old. Will be replaced sometime soon.
Please find summary message, and ACK below. I did replace IP and phone numbers with fake ones.
SIP-trace is taken from Host that Brekeke is installed on.
Brekeke: 192.168.16.18
Lancom: 200.100.50.5
Summary:
N9 8!E:o
!K
!ACK sip:55552222@192.168.16.18:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 200.100.50.5.5:5060;branch=z9hG4bK-50e04aac-c996dadf;rport
Route: <SIP:192.168.16.18:5060;lr>
From: "A1"<sip:22223333@192.168.16.18>;tag=-806073797--2107693741
To: <sip:55552222@192.168.16.18;user=phone>;tag=2378483377
Call-ID: 1273912400@00a0572ebfbb
CSeq: 100 ACK
Max-Forwards: 70
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0147 / 15.11.2017
Content-Length: 0
ACK message:
Session Initiation Protocol (ACK)
Request-Line: ACK sip:55552222@192.168.16.18:5060;transport=udp SIP/2.0
Method: ACK
Request-URI: sip:55552222@192.168.16.18:5060;transport=udp
Request-URI User Part: 55552222
Request-URI Host Part: 192.168.16.18
Request-URI Host Port: 5060
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP 200.100.50.5:5060;branch=z9hG4bK-50e04aac-c996dadf;rport
Transport: UDP
Sent-by Address: 200.100.50.5
Sent-by port: 5060
Branch: z9hG4bK-50e04aac-c996dadf
RPort: rport
Route: <SIP:192.168.16.18:5060;lr>
From: "A1"<sip:22223333@192.168.16.18>;tag=-806073797--2107693741
SIP Display info: "A1"
SIP from address: sip:22223333@192.168.16.18
SIP from address User Part: 22223333
SIP from address Host Part: 192.168.16.18
SIP from tag: -806073797--2107693741
To: <sip:55552222@192.168.16.18;user=phone>;tag=2378483377
SIP to address: sip:55552222@192.168.16.18;user=phone
SIP to address User Part: 55552222
SIP to address Host Part: 192.168.16.18
SIP To URI parameter: user=phone
SIP to tag: 2378483377
Call-ID: 1273912400@00a0572ebfbb
CSeq: 100 ACK
Sequence Number: 100
Method: ACK
Max-Forwards: 70
User-Agent: LANCOM 1783VA (over ISDN) / 10.12.0147 / 15.11.2017
Content-Length: 0