Hi guys,
My friend's company just moved to a new building and now he has a nasty problem. He is using a Hybird 600 with an All-IP Telekom connection. The Hybird is behind a Sophos (Astaro) UTM9 security gateway, which in turn is behind a Fritzbox 7390.
From any extension (S560 system phones) it is possible to call outbound, no problems whatsoever. However, inbound calls are rejected by the Hybird 600 with a " SIP/2.0 404 Not Found" message to the Telekom server, which then ACKs this, the caller then hears the message "Diese Rufnummer ist uns nicht bekannt". The tcpdump capture on the Sophos UTM9 below shows the INVITE received by the Hybird, The 404 Not Found, followed by the ACK sent by Telekom to the Hybird.
The SIP handler in the Sophos UTM9 handles the SIP signalling and RTP port forwarding with the SIP helper function. Since outbound calls work perfect and the incoming SIP INVITE is received by the Hybird 600, we believe a missing or wrong configuration setting in the Hybird is causing the problem. Perhaps the Hybird needs an inbound rule to accept all incoming calls. The basic SIP configuration is identical to what is written in the Elmeg FAQ here
My friend and I would be more than happy if anyone has ideas.
Wish you all a Happy New Year
JockyW
PS:
- in the tcpdump capture, the phone number of the Hybird is edited to [email protected] and the caller number to [email protected]
- the IP address of the Hybird is 192.168.115.146 which is in the internal LAN behind the UTM9 firewall
- the IP address of the Fritzbox is 192.168.174.1 which is the transit network between the WAN uplink of the UTM9 and the Fritzbox. The UTM9 WAN uplink has 192.168.174.202
- we configured the Fritzbox as the SIP registrar for the Hybird as per instructions which can be found here. The same problem occurs with incoming calls, the Hybird responds with "SIP/2.0 404 Not Found"
- as an intermediate workaround, we connected the Hybird to the S0 ISDN of the Fritzbox. This works, but we would like to get the SIP VoIP to work rather sooner than later
My friend's company just moved to a new building and now he has a nasty problem. He is using a Hybird 600 with an All-IP Telekom connection. The Hybird is behind a Sophos (Astaro) UTM9 security gateway, which in turn is behind a Fritzbox 7390.
From any extension (S560 system phones) it is possible to call outbound, no problems whatsoever. However, inbound calls are rejected by the Hybird 600 with a " SIP/2.0 404 Not Found" message to the Telekom server, which then ACKs this, the caller then hears the message "Diese Rufnummer ist uns nicht bekannt". The tcpdump capture on the Sophos UTM9 below shows the INVITE received by the Hybird, The 404 Not Found, followed by the ACK sent by Telekom to the Hybird.
Code:
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
16:50:01.460499 IP (tos 0xb8, ttl 58, id 44642, offset 0, flags [DF], proto UDP (17), length 1297)
217.0.23.68.5060 > 192.168.115.146.5060: SIP, length: 1269
INVITE sip:[email protected]:5060;transport=udp;line=9A98D64CE5B23410ACF5290016150048 SIP/2.0
Max-Forwards: 51
Via: SIP/2.0/UDP 217.0.23.68:5060;branch=z9hG4bKg3Zqkv7i7nwmrk9ls6f3oxgdhp1p5sz1h
To: <sip:[email protected];user=phone>
From: <sip:[email protected];user=phone>;tag=h7g4Esbg_p65542t1483199401m386113c914756618s1_1165197163-1671828516
Call-ID: p65542t1483199401m386113c914756618s2
CSeq: 1 INVITE
Contact: <sip:[email protected];transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Record-Route: <sip:217.0.23.68;transport=udp;lr>
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Min-Se: 900
P-Asserted-Identity: <sip:[email protected];user=phone>
Session-Expires: 1800
Supported: timer
Supported: histinfo
Supported: norefersub
Content-Type: application/sdp
Content-Length: 197
Session-ID: 33dac5d5bff71acad9058a01dd9955c5
Request-Disposition: no-fork
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, INFO, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE
v=0
o=- 751399139 1165196913 IN IP4 217.0.4.102
s=-
c=IN IP4 217.0.4.102
t=0 0
m=audio 11104 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=maxptime:20
a=ptime:20
16:50:01.519591 IP (tos 0xb8, ttl 62, id 13758, offset 0, flags [none], proto UDP (17), length 477)
192.168.115.146.5060 > 217.0.23.68.5060: SIP, length: 449
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 217.0.23.68:5060;branch=z9hG4bKg3Zqkv7i7nwmrk9ls6f3oxgdhp1p5sz1h
Record-Route: <sip:217.0.23.68;transport=udp;lr>
From: <sip:[email protected];user=phone>;tag=h7g4Esbg_p65542t1483199401m386113c914756618s1_1165197163-1671828516
To: <sip:[email protected];user=phone>;tag=9A98D64CE5B23410ACF5290016150048
Call-ID: p65542t1483199401m386113c914756618s2
CSeq: 1 INVITE
Content-Length: 0
16:50:01.543965 IP (tos 0xb8, ttl 58, id 44643, offset 0, flags [DF], proto UDP (17), length 522)
217.0.23.68.5060 > 192.168.115.146.5060: SIP, length: 494
ACK sip:[email protected]:5060;transport=udp;line=9A98D64CE5B23410ACF5290016150048 SIP/2.0
Max-Forwards: 70
Via: SIP/2.0/UDP 217.0.23.68:5060;branch=z9hG4bKg3Zqkv7i7nwmrk9ls6f3oxgdhp1p5sz1h
To: <sip:[email protected];user=phone>;tag=9A98D64CE5B23410ACF5290016150048
From: <sip:[email protected];user=phone>;tag=h7g4Esbg_p65542t1483199401m386113c914756618s1_1165197163-1671828516
Call-ID: p65542t1483199401m386113c914756618s2
CSeq: 1 ACK
Content-Length: 0The SIP handler in the Sophos UTM9 handles the SIP signalling and RTP port forwarding with the SIP helper function. Since outbound calls work perfect and the incoming SIP INVITE is received by the Hybird 600, we believe a missing or wrong configuration setting in the Hybird is causing the problem. Perhaps the Hybird needs an inbound rule to accept all incoming calls. The basic SIP configuration is identical to what is written in the Elmeg FAQ here
My friend and I would be more than happy if anyone has ideas.
Wish you all a Happy New Year
JockyW
PS:
- in the tcpdump capture, the phone number of the Hybird is edited to [email protected] and the caller number to [email protected]
- the IP address of the Hybird is 192.168.115.146 which is in the internal LAN behind the UTM9 firewall
- the IP address of the Fritzbox is 192.168.174.1 which is the transit network between the WAN uplink of the UTM9 and the Fritzbox. The UTM9 WAN uplink has 192.168.174.202
- we configured the Fritzbox as the SIP registrar for the Hybird as per instructions which can be found here. The same problem occurs with incoming calls, the Hybird responds with "SIP/2.0 404 Not Found"
- as an intermediate workaround, we connected the Hybird to the S0 ISDN of the Fritzbox. This works, but we would like to get the SIP VoIP to work rather sooner than later
Zuletzt bearbeitet:
