[Resolved for now] No outgoing, but can receive calls

[Phone-101]

Hello,

I am trying to make my newly installed Poly ATA 402 work, I was using an Obi 100 that has an hardware failure.

I can see the SIP registration and get incoming calls that get logged in my FPL web portal. No outgoing calls whatsoever will show in the log.

I followed the pdf guide for the Obi 200/300 and used the voip4 server to connect.

I can receive incoming calls but no outgoing possible, not even to another Fongo number.

Any hints on why ?

My Free phone Line Account is registered on the SP2 and I got another Voip service on SP1 that I can make Outgoing calls with no problems.

Any hints to troubleshoot ?

ATA Call history :
Call 1 12/26/2024 04:13:26
04:13:26 From PH1 To SP2(xxxxxxxxxx)
04:13:58 Call Ended

Thanks for your help.

[Liptonbrisk]

I am trying to make my newly installed Poly ATA 402

Do you mind if I ask where you bought it from? Just curious.

Any hints on why ?

In the ATA's call history, is the full phone number being sent via SP2? (xxxxxxxxxx)? I'm guessing that it is, but please check anyway.

The call disconnects approximately 32 seconds later. I don't know if that's because you are hanging up the call (doubt it). Drops after 32 seconds is often due to ACK (Acknowledgement) not being received, and it almost suggests the issue is SIP ALG or NAT firewall related. I usually associate SIP ALG issues with incoming call and registration problems, but it can still interfere with outgoing calls.

If you're using voip4.freephoneline.ca and also using a random X_UserAgentPort, I doubt SIP ALG is the problem.

Regardless,

1. Disable SIP ALG in your TP-Link TD-8817: https://www.tp-link.com/ca/support/faq/343/ (Uncheck SIP ALG box. Then click "Save" button. Reboot device. Wait for it to be fully up and running before proceeding). If that is not your modem/router combo, then provide the brand and model number. Getting SIP ALG disabled in your devices is important.

2. Are you also using your own separate router in addition to the TP-LINK TD-8817? If so, what is the brand and model?

3. In your ATA's webUI, Navigate to Voice Services-->SP2-->_UserAgentPort

a) X_UserAgentPort should be a random UDP port number between 30000 and 60000. Just pick a port number in that range.
If you already have a random number in that range, simply enter a new one in that range.
By using a high random port you help to thwart SIP scanners/hackers.

Do not use the same X_UserAgentPort for any other SP. Pick a different X_UserAgentPort in the same range for other SPs.

Never use UDP 5060 or 5061 for X_UserAgentPort.

Click "Submit" (or save settings).

4. Navigate to Service Providers-->ITSP Profile B-->SIP-> X_UsePublicAddressInVia

a) Enable UsePublicAddressInVia (you will have to uncheck default box).

b) Also ensure that X_DiscoverPublicAddress is enabled (it is by default).

Submit/ Save settings


5. Navigate to Service Providers–>ITSP Profile B–>General
a. Use DigitMap: (1xxxxxxxxxx|011XX.S3|[2-9]xxxxxxxxx|*98|[2-9]11|988)

(b. By the way, if you want outbound calls to mostly use Freephoneline, then set PrimaryLine under Physical Interfaces-->PHONE Port (the one used for outbound calls) to SP2.)


6. Click "Submit" or save settings. Reboot ATA

7. Test again with outbound calls.

8. If there's still a problem,

a) check your ATA's call log again. Ensure that the full and proper phone number is being sent.

b) Basically you want to see whether the TP-LINK's NAT firewall or any other router setting is causing the problem.

i) One way to do this if your ISP uses PPPoE AND allows multiple PPPoE sessions (contact your ISP to make sure), is to perform PPPoE passthrough using your ATA. In your ATA, you would navigate to Router Configuration-->WAN Settings-->Internet Settings-->Addressing Type. You would change that to PPPoE. Then you would need both your PPPoE Username and Password from your ISP. You need to ensure you don't make typos when entering PPPoE Username and PPPoE Password in your ATA's web user interface.

ii) Otherwise, try to get your ISP's modem-router combo in bridge mode. Contact your ISP first for more information and help. After testing, disable bridge mode (revert). Ask your ISP how to do this if you need assistance. Everything on your LAN will be unprotected while the modem-router combo is in bridge mode. So, don't leave it in bridge mode for long if you're not using your own router in addition to whatever your ISP gave you.

c) If you're able to use PPPoE passthrough or use bridge mode then don't do step iv below.

I would very briefly, because this is dangerous to leave an ATA unprotected by any firewall, test to see whether your modem/router combo's firewall is causing problems.

iii) Thankfully, the Poly 402 does have a firewall. Navigate to Router Configuration-->Firewall and DMZ-->Firewall Settings. Check "Enable" box. Then Submit/save settings. Reboot.

The ATA's firewall shouldn't cause a problem with calls.

iv) Then put the ATA's IP address in DMZ in your TP-LINK TD-8817 would be one way to test: https://static.tp-link.com/res/down/doc ... _V8_UG.pdf (page 33). Dial ***1 to hear your ATA's LAN IP.

If anything in step 8 fixes the problem, then you know the issue is because of TP-Link's NAT firewall or router features. It's not a good idea to leave the Poly 402 in DMZ. After testing, if you used DMZ, remove the IP address entered in step iv. Afterwards, you can disable the firewall in the Poly 402 (refer to step iii) provided you're not using PPPoE passthrough in the ATA and/or provided TP-Link 8817 modem/router combo isn't in bridge mode. Basically, if the ATA is unprotected by any hardware firewall, then enable the firewall in the ATA (PPPoE passthrough or bridge mode means TP-Link's firewall isn't protecting the ATA).

It's not ideal to use port forwarding and, especially, DMZ. They're potential security risks. If I discovered I needed to port forward the UDP port defined by X_UserAgentPort, which is used for SIP signalling, I would ensure that my ISP allows either bridge mode or PPPoE passthrough and use my own separate router (I do that as standard practice).


I just tested while registered on voip4.freephoneline.ca:6060, and outbound calls are working fine for me on an OBi202. Also, all of my other service providers are working fine as well (but that's not extremely relevant since they're all configured differently) on the same ATA. Poly 402 is basically the same ATA, as far as using it with Freephoneline.


When I see 32 second calls drops, I often find it's due to ACK (Acknowledgement) not being received. Common causes are SIP ALG, NAT firewalls blocking ports, and Freephoneline not being registered in the ATA (if you're receiving incoming calls, then FPL is registered).

[Phone-101]

Do you mind if I ask where you bought it from? Just curious.

Thank you for the fast reply.

I purchased mine at PC-Canada : MFGR #: 8F3H5AA#ABA it was on pre-sale for Boxing Day.

I will check everything you posted, all settings seem ok but I will double check.

Rapidly from reading 1 time.

1) My TP-Link does not have a SIP ALG setting. I see a SPI options but I don't think it would be a good idea to disable it?

I will try to Telnet in my TP-Link to disable SIP ALG

8) c) iii) I don't see any firewall settings in my ATA, maybe the Obi 300 is different from the Poly 402 ?

I was planning to use either a OpenWRT (using an X86 fanless mini-pc) with my router-DSL Modem combo in bridge mode or I have a D-Link DSL-520B as an emergency backup which of the 2 would fix my firewall issue ?

Why is my FPL service working with my Obi 100 but not the ATA 402 any idea ?

My Obi 100 has a hardware defect, it looses registration after a while some times hours sometimes days on 2 different Voip services. When I power it off and on after 1 hour of cooling sometimes I get a red light flashing. When I try to log in its asking me to keep the power on while it updates the firmware. Probably a corrupted memory or some cold solder joints needing a refresh.

Thank you.

[Liptonbrisk]

I purchased mine at PC-Canada : MFGR #: 8F3H5AA#ABA it was on pre-sale for Boxing Day.

Interesting. Thank you.

1) My TP-Link does not have a SIP ALG setting. I see a SPI options but I don't think it would be a good idea to disable it?

Only when dealing with step 8 (above)--and only briefly while testing to try to eliminate what's causing the issue

It's generally not a great idea to disable firewalls. It's also not a great idea to use DMZ and port forwarding either (port forwarding can be done if no other option exists, but it's not advisable). SPI can be useful security feature and is typically safer to have it enabled, but if it's implementation is buggy or overly aggressive, it's up to you to decide whether it's useful.

The SPI (stateful packet inspection) option might interfere with SIP traffic, and I'm under the impression that it's disabled by default in your TP-LINK modem/router combo. If it's enabled, I suspect you turned it on at some point.

1) Under Advanced Setup-->disable the SPI option. Click "save". Reboot the router. Wait for it to be fully up and running. Then reboot the ATA. Then test with outgoing calls. I would do this step at least to test. If disabling SPI doesn't help, then re-enable it.

I will try to Telnet in my TP-Link to disable SIP ALG

The setting may be unavailable depending on firmware used (particularly if issued by your ISP). The TP-Link website link I provided previously indicates that it's intended for TD-8817 though.

I don't know how useful this is for you: https://support.kixie.com/hc/en-us/arti ... ce-and-CLI

8) c) iii) I don't see any firewall settings in my ATA, maybe the Obi 300 is different from the Poly 402 ?

I don't have an OBi300. OBi302 and OBi202 have firewalls.

Wow. I just skimmed through https://kaas.hpcloud.hp.com/pdf-public/ ... n-US-1.pdf. It appears that Poly removed the firewall and router features in the Poly 402 from previous Obihai 2-phone port ATA models. I didn't realize that. My apologies. That means it is dangerous to test without a firewall since the ATA will be unprotected. Also, I doubt PPPoE passthrough using the ATA is an option.

I was planning to use either a OpenWRT (using an X86 fanless mini-pc) with my router-DSL Modem combo in bridge mode or I have a D-Link DSL-520B as an emergency backup which of the 2 would fix my firewall issue ?

Without disabling your firewall and testing, it's difficult to determine that it's a firewall issue, specifically. I don't know that it is for sure.

OpenWRT would provide more flexibility, but I'm not sure a firewall problem exists.

Why is my FPL service working with my Obi 100 but not the ATA 402 any idea ?

No, and I’m not sure why you’re getting errors. With respect to SIP provisioning and signalling, they should be very similar. OBi100 doesn't have the X_UsePublicAddressInVia setting and offers less audio codecs than Poly 402.

2. If disabling X_UsePublicAddressInVia works, I would find that surprising. It adds your public WAN IP address in the outbound Via header. Obviously if the FPL proxy server sends packets to the ATA's LAN IP address instead, they would never arrive since LAN IP addresses are not routable on the public internet.If UsePublicAddressInVia is enabled in the Poly 402 ATA, it inserts your public WAN IP in SIP Via headers, helping to ensure the Freephoneline proxy server being used sends responses directly to your public WAN IP. If SPI is enabled on the TP-Link router, maybe SPI blocks incoming traffic that matches these responses because SPI treats unsolicited WAN traffic as a potential threat. However, they're not really unsolicited since you're initiating an outbound call from your LAN. Possibly SPI is overly aggressive or isn't tracking the session state properly (buggy).

Anyway, you can try disabling X_UsePublicAddressinVia to see if that makes any difference. If it doesn't, I would re-enable it. You could also try disabling both SPI and X_UsePublicAddressinVia to see if outbound calls suddenly work.

3. Check your codec settings. FPL only supports G.711u and G.729a (G.729a sounds worse).
Navigate to Voice Services-->SP2 Service-->X_CodecProfile to determine what codec profile is being used with Freephoneline.
Then navigate to the corresponding Codec profile: Codecs-->Codec Profile used for Freephoneline
For G711U Codec, ensure that it's Priority 1.
Set G729 Codec to Priority 2.
Disable the other codecs. Don't disable Telephone event, Fax event, T38Enable, and T38ECM. Click Submit. Reboot if prompted.
Then test. Maybe it's a codec mismatch issue. The Poly 402 does support more audio codecs than the OBi100.

4. Try voip2.freephoneline.ca:5060 to see if that makes any difference for you. I'm not noticing a problem on voip4.freephoneline.ca:6060, but maybe there is an issue that I'm not experiencing with that server.

5. Your ATA appears to be running firmware version 4.0.1.6480. The latest is version 4.0.2.6778 Rev.A.

This is the firmware version for your ATA: https://support.hp.com/ca-en/drivers/sw ... p-339120-1
(I am not responsible for problems resulting from failed firmware updates). Possibly a firmware update helps.


6. A syslog might be useful for capturing what happens on SP2. Does this work for you? viewtopic.php?p=80667#p80667. Also, see https://kaas.hpcloud.hp.com/pdf-public/ ... n-US-1.pdf (page 107). If you're going to offer the log, provide the text from the start of picking up the phone and dialing until the call drops--and not a screenshot, please.


Here's the parameter reference guide: https://docs.poly.com/bundle/poly-ata-p ... eters.html.

[Phone-101]

Thank you for all the detailed tips.

Surprisingly, everything started working before I had a chance to try some more settings modifications.

I will leave it as is for now just to see if I get the same registration issues I was getting with my Obi 100.

So far so good.

Thanks again, have a great new year.

[Liptonbrisk]

Surprisingly, everything started working before I had a chance to try some more settings modifications.

That is strange. Without syslogs comparing 32 second drops with working outbound calls, i have no further comment except that using outdated ATA firmware probably isn’t advisable (step 5 above).

I’ll mark this thread as being resolved for now.

I will leave it as is for now just to see if I get the same registration issues I was getting with my Obi 100.

Power adapters/supplies for ATAs are often susceptible to electrical surges related to storms and power outages). If you have another compatible power adapter available, you might want to try it just to see if your ATA still works (but the description you provided suggested internal hardware failure). If the OBi100 is stable, you might be able to update firmware yourself using modded firmware from Obifirmware (search for it).

I have a whole house surge protector in the breaker box in my basement, and all of my ATAs and IP Phones are either plugged into a UPS or battery backup. I haven't had an ATA die since 2009.

My neighbourhood is horrible for power fluctuations. The power flickers off and back on at least twice a month (sometimes multiple times a week). I always hear my battery backups kick in, practically every week. It's nuts. My neighbours don't even notice, except when their lights flicker momentarily. Anyway, I've had to protect all of my electronics. I find cheap surge protectors in power bars are often unreliable.

Also, keep ATAs in well-ventilated areas. Don't stack objects up against them or otherwise block airflow to them.

Lastly, don’t connect an ATA to a phone jack in a home without first disconnecting the telephone company’s wiring at the demarc. Electricity from the telephone company’s wiring can fry the ATA.

Thanks again, have a great new year.

I wish you a Happy New Year as well!