Getting 2Talk VOIP to work on a second router

Forums › VoIP › Getting 2Talk VOIP to work on a second router

allistar

33 posts

Geek

#303900 18-Mar-2023 18:13

Hello. I'm trying to get 2talk VOIP working for a friend. Their scenario is they have a router (provided by Skinny, using ADSL) that has no phone jacks. I have a Netcomm NF4V that does have phone jacks. I figure if I can get it working on my network (which is Fibre, the router is provided by Vodafone) then I should be able to get it to work on theirs. Here's my setup:

Vodafone router on 192.168.0.1 -> Netgear 8 port switch -> NF4V.

If I plug into the NF4V on one of the LAN ports (not the WAN port) then the wifi on the NF4V gives internet access. I disable DHCP and manually assign a 192.168.0 address to the NF4V. This works well. When going into the NF4V interface and running the ping diagnostic it doesn't display anything. I suspect it's trying to use a WAN connection which is doesn't have. At this point the NF4V works well in all regards other than VOIP doesn't work.

The only way I can get a WAN connection to work is if the NF4V is on a different subnet (192.168.2.1) running its own DHCP server and plugging the Vodafone router into the WAN port of the NF4V. The issue with this is that I can't port forward from the Vodafone network to the NF4V network.

I want the NF4V to be on the same subnet as the main router.

For VOIP setup I have port forwarded 5060, 5061 and 50600 on the main router to the NF4V address for both UDP and TCP. In the VOIP status screen it says "Registration status = down".

Is there a way to get this working? Do I need to get the WAN interface of the NF4V working, or use bridged mode or a DMZ?

Thanks in advance.

richms

28032 posts

Uber Geek

Trusted

Lifetime subscriber

#3051656 18-Mar-2023 18:47

You cant do what you are wanting with the gear you have.

You either have to have the WAN on the netcomm be its internet feed and have it do nat to its wifi and LAN ports and operate ifs voip out that connection, or else use it as a dumb AP with no voip or nat happening by misusing it as an AP with DHCP disabled and hope that the thing doesnt keep rebooting because it runs out of ram from the constant failure to get an internet connection.

You can port forward fine with double nat, you have to do it on both routers, once to the wan of the netcomm on the internet router, and again to the final device on the netcomm.

Richard rich.ms

Tradepub

Free professional, reference and technical white papers (affiliate link).

yitz

2052 posts

Uber Geek

#3051684 18-Mar-2023 21:15

allistar:

I want the NF4V to be on the same subnet as the main router

Assuming you are just wanting to use the NF4V as a simple ATA to plug an analogue phone into and not to use its LAN ports or Wi-Fi for internet access or anything else fancy then you can just set it up in Ethernet WAN mode with NAT which by the sounds of it you have already achieved in one of your scenarios. If you want to access the management UI from 192.168.0.x then just enable WAN side access under Management > Access Control > Services Control. The SIP client runs on the NF4V so will be attached to the WAN IP i.e. 192.168.0.x so there is only single NAT.

halper86

545 posts

Ultimate Geek

ID Verified

#3051699 18-Mar-2023 22:19

I have a working setup like your friend is trying to achieve:

As mentioned above, plug skinny router lan to netcomm wan, set wan setting to dhcp, turn wifi/ap off.

The internet light and voip lights on the nf4v should be on when working.

DeepBlueSky

547 posts

Ultimate Geek

#3051924 19-Mar-2023 15:34

Hi guessing you connecting and old analog phone to the phone connector on the router, my 2 cents worth I didn’t go down that route due my router not having the phone ports. That was a few years back now.

I looked at getting a box at that time that was not too expensive basically a base station with a phone port on the back designed for using existing analog phones and connecting them to VOIP though a router.

In the end I picked up a Yealink W76P High-performance DECT IP Phone from PB Tech This comes with the base station plus a DECT phone I thing you can have up to 9 extra handsets. It was the easiest works great with 2talk and I think from memory there was a page to show you how to configure it.

I have also converted my mother in law over to this setup when her new build did not have a copper line installed not done now.

Hope this helps.

allistar

33 posts

Geek

#3052734 21-Mar-2023 10:47

Hi all,

Thanks for your help. We've made progress. The key was getting the WAN on the router set up on a different subnet to the main network. Now the secondary router (which is a D-LINK at my friends house) is on 192.168.2.* while the main network (the Skinny router) is 192.169.1.*. The D-LINK has a functioning wifi, can see the internet with no problems and now says it has a functioning WAN connection. We're port forwarding 6050/6051/60500 from the primary router to the D-LINK. VOIP on the D-LINK says it's registered and there's a dial tone. The 2talk website says there's an active device. So far so good. However, when trying to make a call the VOIP status on the D-LINK changes to "fault" and the dial tone is no longer there. It seems like we're so close to having this working.

Does anyone have any pointers on what could cause a VOIP connection to register, and then fault when you try to use it?

Thanks again.

fe31nz

1206 posts

Uber Geek

#3053077 21-Mar-2023 23:51

VOIP connections are done in two parts, the SIP part for the registration and dialling, and the RTP/RTSP part for the actual telephone data stream. With my 2Degrees VOIP, the SIP connection requires UDP port 5060 to be forwarded to my FritzBox. The RTP/RTCP pairs of UDP connections are done on ports 7078/7079 up to 7108/7109 and so I need to have UDP ports 7078-7109 forwarded to my FritzBox also. The way it works is that SIP is used to register a connection with the VOIP server, and to accept incoming call setup or send outgoing call setup. The call setup negotiates the RTP/RTCP port pair numbers, after which the actually phone data is sent on the RTP port and the connection is managed on the RTCP port. The usual pattern of port use is the first concurrent call uses ports 7078/7079, the second concurrent call uses 7080/7081 and so on up to the maximum limit of concurrent calls.

So you need to find documentation on what ports your VOIP service uses for RTP/RTCP and forward them also. Or if your router is capable of it, or you have some other way to do it (eg mirror port on your switch), you can capture the SIP packets attempting to make a connection and use Wireshark to display them and see the RTP port number negotiated in the SIP packets. Only the RTP port is negotiated directly, the corresponding RTCP port is always 1 greater than the RTP port number.

There are some further problems with the use of UDP for VOIP - when outbound UDP connections happen, your router records the fact the UDP traffic is happening on a port and keeps that port open for incoming packets for a certain time after the last outbound or inbound UDP packet was seen, then it will automatically close the port again. If that timeout is less than the keepalive time used by your VOIP connection, the port will be closed in the middle of the connection. So you either need to have control of that timeout and make sure it is long enough, or you need to just permanently open the VOIP ports. SIP connections can be TCP or UDP, depending on what the VOIP server prefers, but they are usually UDP. If they are TCP, the connection will be maintained by the TCP protocol as timeout control is part of TCP, but not UDP. RTP/RTCP is always UDP, and while the RTP port is normally kept busy, the RTCP port only has occasional traffic and can timeout.

allistar

33 posts

Geek

#3054437 25-Mar-2023 14:27

Thanks for your help everyone. We can now make outgoing calls with no issues. Incoming calls however crash the voip client on the router. The router is a D-LINK DSL-X1852E which is also branded as an AX1800. The debug log shows the crash of the voip client when an incoming call is answered. The phone rings. Here's the relevant part of the log:

2023-03-24 13:20:22 [Warning] kernel: 1679620822.762234: [mapd][steer_exec_csbc_fsm][1905]CLI 2 6c:c7:ec:08:d8:bf Event=2 BTMState=4 ForcedState=0
2023-03-24 13:20:22 [Warning] kernel: 1679620822.784516: [mapd][csbc_enter_btm_active_unfriendly][1800]Client 2 6c:c7:ec:08:d8:bf is now BTM Active unfriendly
2023-03-24 13:20:22 [Warning] kernel: 1679620822.943819: [mapd][chan_mon_handle_steer_complete][329]steer complete received in wrong state... ignore
2023-03-24 13:20:25 [Informational] syslog: INFO: [SIP Tx] ua_id:393221, ts_id:18, ts_type:INVITE Server, fsm_msgid:1, ts_state:0
2023-03-24 13:20:25 [Informational] syslog: INFO: [SIP Tx] SITS change state, ua_id:393221, ts_id:18, ts_state:Proceeding
2023-03-24 13:20:25 [Informational] syslog: [SIP Tx] siptx_send_req => conn_id:0x60005, msg:289
2023-03-24 13:20:25 [Informational] syslog: [SIP Tx] siptx_make_data_req => ts_id:18, conn_td:0x60005, msg:289 me:0
2023-03-24 13:20:25 [Informational] syslog: [SIP Tx] siptx_send_req => soc:131073, id:0x60005
2023-03-24 13:20:25 [Informational] syslog: [SIP Tx] siptx_send_req => ip:27.111.14.65, port:5060
2023-03-24 13:20:25 [Informational] syslog: INFO: [CM] start tone, line:0, tone_type:40
2023-03-24 13:20:25 [Informational] syslog: INFO: [CM-Media] Type II call-ID with ACK, line:0
2023-03-24 13:20:25 [Informational] syslog: [SIP] send msg request : 291
2023-03-24 13:20:25 [Informational] syslog: INFO: [SIP Tx] ua_id:393221, ts_id:18, ts_type:INVITE Server, fsm_msgid:0, ts_state:1
2023-03-24 13:20:25 [Informational] syslog: [SIP Tx] siptx_send_req => conn_id:0x60005, msg:291
2023-03-24 13:20:25 [Informational] syslog: [SIP Tx] siptx_make_data_req => ts_id:18, conn_td:0x60005, msg:291 me:0
2023-03-24 13:20:25 [Informational] syslog: [SIP Tx] siptx_send_req => soc:131073, id:0x60005
2023-03-24 13:20:25 [Informational] syslog: [SIP Tx] siptx_send_req => ip:27.111.14.65, port:5060
2023-03-24 13:20:25 [Warning] kernel: do_page_fault() #2: sending SIGSEGV to sipclient for invalid read access from
2023-03-24 13:20:25 [Warning] kernel: 00000000 (epc == 77205e80, ra == 77205e7c)
2023-03-24 13:20:25 [Warning] kernel: CPU: 3 PID: 3459 Comm: sipclient Tainted: P O 3.18.21 #174
2023-03-24 13:20:25 [Warning] kernel: task: 8a042100 ti: 86f2c000 task.ti: 86f2c000
2023-03-24 13:20:25 [Warning] kernel: Status: 01000013^IUSER EXL IE
2023-03-24 13:20:25 [Warning] kernel: Cause : 40809408
2023-03-24 13:20:25 [Warning] kernel: BadVA : 00000000
2023-03-24 13:20:25 [Warning] kernel: PrId : 0001992f (MIPS 1004Kc)
2023-03-24 13:20:25 [Warning] kernel: Call Process maps
2023-03-24 13:20:25 [Warning] kernel: 00400000-0053c000 r-xp 00000000 1f:03 1396 /userfs/bin/sipclient
2023-03-24 13:20:25 [Warning] kernel: 0054c000-00567000 rw-p 0013c000 1f:03 1396 /userfs/bin/sipclient
2023-03-24 13:20:25 [Warning] kernel: 00567000-0056b000 rwxp 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 00633000-006c7000 rwxp 00000000 00:00 0 [heap]
2023-03-24 13:20:25 [Warning] kernel: 20000000-20200000 rw-s 00000000 00:01 0 /SYSV12345678 (deleted)
2023-03-24 13:20:25 [Warning] kernel: 72014000-72015000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 74815000-75014000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 75014000-75015000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 75015000-75814000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 75814000-75815000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 75815000-76014000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 76014000-76015000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 76015000-76814000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 76814000-76815000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 76815000-77014000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 77014000-7701e000 r-xp 00000000 1f:03 1072 /lib/libubox.so
2023-03-24 13:20:25 [Warning] kernel: 7701e000-7702d000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 7714c000-7714d000 rw-p 00003000 1f:03 1057 /lib/librt-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 7714d000-77160000 r-xp 00000000 1f:03 1053 /lib/libpthread-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 77160000-7716f000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 7716f000-77170000 r--p 00012000 1f:03 1053 /lib/libpthread-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 77170000-77171000 rw-p 00013000 1f:03 1053 /lib/libpthread-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 77171000-77173000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 77173000-77176000 r-xp 00000000 1f:03 985 /lib/libdl-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 77176000-77185000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 77185000-77186000 r--p 00002000 1f:03 985 /lib/libdl-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 77186000-77187000 rw-p 00003000 1f:03 985 /lib/libdl-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 77187000-7719d000 r-xp 00000000 1f:03 1030 /lib/libm-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 7719d000-771ac000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 771ac000-771ad000 rw-p 00015000 1f:03 1030 /lib/libm-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 771ad000-771d6000 r-xp 00000000 1f:03 1021 /lib/libgcc_s.so.1
2023-03-24 13:20:25 [Warning] kernel: 771d6000-771e6000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 771e6000-771e7000 rw-p 00029000 1f:03 1021 /lib/libgcc_s.so.1
2023-03-24 13:20:25 [Warning] kernel: 771e7000-771ec000 r-xp 00000000 1f:03 977 /lib/libcompileoption.so
2023-03-24 13:20:25 [Warning] kernel: 771ec000-771fc000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 771fc000-771fd000 rw-p 00005000 1f:03 977 /lib/libcompileoption.so
2023-03-24 13:20:25 [Warning] kernel: 771fd000-77222000 r-xp 00000000 1f:03 902 /lib/libadam.so
2023-03-24 13:20:25 [Warning] kernel: 77222000-77231000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 77231000-77232000 rw-p 00024000 1f:03 902 /lib/libadam.so
2023-03-24 13:20:25 [Warning] kernel: 77232000-7723a000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 7723a000-7723c000 r-xp 00000000 1f:03 1065 /lib/libtcapi.so.1
2023-03-24 13:20:25 [Warning] kernel: 7723c000-7724b000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 7724b000-7724c000 rw-p 00001000 1f:03 1065 /lib/libtcapi.so.1
2023-03-24 13:20:25 [Warning] kernel: 7724c000-7724e000 r-xp 00000000 1f:03 1018 /lib/libecntevent.so
2023-03-24 13:20:25 [Warning] kernel: 7724e000-7725d000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 7725d000-7725e000 rw-p 00001000 1f:03 1018 /lib/libecntevent.so
2023-03-24 13:20:25 [Warning] kernel: 7725e000-772d2000 r-xp 00000000 1f:03 974 /lib/libcfg_clisvc.so
2023-03-24 13:20:25 [Warning] kernel: 772d2000-772e2000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 772e2000-772eb000 rw-p 00074000 1f:03 974 /lib/libcfg_clisvc.so
2023-03-24 13:20:25 [Warning] kernel: 772eb000-772fd000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 772fd000-77303000 r-xp 00000000 1f:03 1044 /lib/libmxml.so.1.4
2023-03-24 13:20:25 [Warning] kernel: 77303000-77313000 ---p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 77313000-77314000 rw-p 00006000 1f:03 1044 /lib/libmxml.so.1.4
2023-03-24 13:20:25 [Warning] kernel: 77314000-7731b000 r-xp 00000000 1f:03 900 /lib/ld-uClibc-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 77328000-7732a000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 7732a000-7732b000 r--p 00006000 1f:03 900 /lib/ld-uClibc-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 7732b000-7732c000 rw-p 00007000 1f:03 900 /lib/ld-uClibc-0.9.33.2.so
2023-03-24 13:20:25 [Warning] kernel: 7732c000-7732d000 rw-p 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 7f9a8000-7f9c9000 rwxp 00000000 00:00 0
2023-03-24 13:20:25 [Warning] kernel: 7fff7000-7fff8000 r-xp 00000000 00:00 0 [vdso]
2023-03-24 13:20:25 [Warning] kernel:
2023-03-24 13:20:25 [Warning] kernel: Call Process Trace
2023-03-24 13:20:25 [Warning] kernel: epc=77205e80,esp=738128e0,era=77205e7c
2023-03-24 13:20:45 [Warning] kernel: fxsGetChan [0] HookState [1]
2023-03-24 13:20:46 [Warning] kernel: fxsGetChan [0] HookState [0]

I've asked D-LINK support but haven't had a response yet (after 4 days).

It's more difficult to diagnose this as it appears to be a fault in the router itself. I wouldn't expect it to get a page fault.

For reference, here's the setup:

- the D-LINK is connected via the WAN port to the main Skinny router.
- the D-LINK has internet access and connected wifi clients have net access too.
- SIP and RTSP ports on both TCP and UDP and port forwarded from the Skinny route to the D-LINK.

Any help is appreciated.

radicall

94 posts

Master Geek

Trusted

Radicall

#3054539 25-Mar-2023 15:04

My Network Engineers suggest the following:

From the log, it appears that the voip client on the router crashes when an incoming call is answered due to a memory access violation. The error message indicates that the crash occurred due to an invalid read access at memory address 0x00000000.

To fix the memory access violation, the root cause of the issue needs to be identified. Here are some steps that could help in resolving the issue:

Check if there are any firmware updates available for the D-LINK DSL-X1852E router. If so, update the router's firmware to the latest version. Firmware updates often contain bug fixes and performance improvements that can help resolve issues such as memory access violations.
Check if any recent changes were made to the router's configuration or network setup. Roll back any recent changes that could be causing the issue, and check if the problem persists.
If the issue still persists, try disabling any SIP ALG (Application Layer Gateway) features on the router. SIP ALG is a feature that helps in handling SIP traffic for VoIP applications. However, in some cases, SIP ALG can cause issues such as memory access violations. Disabling this feature might help resolve the issue.
If none of the above steps work, the issue could be related to a hardware fault in the router. In this case, it might be necessary to contact the manufacturer for further assistance or to consider replacing the router.

It is important to note that diagnosing and fixing memory access violations can be a complex task that requires technical expertise. It is recommended to seek the help of a qualified network engineer or IT professional if the above steps do not resolve the issue.

Hope that helps...

______________________________________ www.radicall.co.nz ________________________________________

Be Successful WITH US! - Light ideas for YOUR SUCCESS - Business Solutions OF A NEW AGE - Result Driven IDEAS _______________________________________________________________________________________________

allistar

33 posts

Geek

#3054561 25-Mar-2023 15:54

Thanks for the reply. The router is running the latest firmware. It's brand new (from Harvey Norman) and was bought for the purpose of VOIP. We'll try disabling the SIP ALG on both routers to see if that makes a difference.

Thanks again.