Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't register VoIP #1165

Open
vmsh0 opened this issue Apr 16, 2023 · 2 comments
Open

Can't register VoIP #1165

vmsh0 opened this issue Apr 16, 2023 · 2 comments

Comments

@vmsh0
Copy link

vmsh0 commented Apr 16, 2023

NB: Before submitting an issue, check if there is one already open that suits the problem you are having!

Device Model/Firmware: tg789vac v2
GUI Version: 9.6.65-89342d7b

Please go to Cards >> GUI Settings >> Debug Report and press the Generate button.
Attach the debug file here: DebugHelper2023-04-16-1123.tar.gz

Description of problem, HOW TO REPRODUCE, Media/Photos:
Can't get VoIP to register. I'm with a third party VoIP provider for which I know the username and password (so no guessing or extracting from ISP configs). I have configured it in the Telefony card but it's not registering. How should I debug the issue?

image

image

@eimparas
Copy link

eimparas commented May 4, 2023

i had the same issue a while back ,on a tg789vac v2 runing ansuel when i tryed registering a custom voip provider .
Thier sip proxy were for example , ims.domain.com i entered that on the primary proxy and failed to register. I did a packet capture with wireshark , and found that router was sending ims.domain.com.LAN i overcame this by entering the server's IP *

  • this could have some implecations though , these types of servers are behind load balancers , and the ip on the domain changes depending the load of the voip provider . Thankfully i didnt have any issue till now , but i have to mention this so you are aware

@FrancYescO
Copy link
Collaborator

i had the same issue a while back ,on a tg789vac v2 runing ansuel when i tryed registering a custom voip provider . Thier sip proxy were for example , ims.domain.com i entered that on the primary proxy and failed to register. I did a packet capture with wireshark , and found that router was sending ims.domain.com.LAN i overcame this by entering the server's IP *

  • this could have some implecations though , these types of servers are behind load balancers , and the ip on the domain changes depending the load of the voip provider . Thankfully i didnt have any issue till now , but i have to mention this so you are aware

no sure, but maybe this can happen when leaving the realm empty

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants