Search results

Agreed. Except for my Nortel 1140e phones. I expect that the Nortel phone is an outlier as you shouldn’t have to use the same port number for both ends of the connection. But that was the only way I could get the phones to stay connected.

It’s been a while since I’ve had a new Incredible build but from memory just hitting detect network settings populated both fields. I suspect that this won’t fix your issue. It will most likely be a firewall issue.

Why do you need that granularity? The CDR does give you call duration in minutes and seconds.

What phone are you using? I struggled for long time to get a Nortel 1140e to run on pjsip. In the end I had to specify the port explicitly in the phone configuration. The phone would register but didn’t re-register after the time out period.

To some extent compulsory voting minimizes the damage they cause.

That doesn't mean you aren't caught up in the breach. :D One of the breaches here was a finance company and has included people who were customers more than 3 takeovers ago. They have never done business with the company under it's current name.

I just don't understand why businesses are allowed to keep former customer's data forever. It happens here in Oz too.

I have no knowledge of GoIP but GSM is very old technology so I doubt you will be able to identify the original caller. If it was possible it would be dependent on the GoIP gateway being able to pass the caller’s information to the SIP world.

This is line 1571. [2024-04-05 18:54:30] VERBOSE[77814][C-0000000e] pbx.c: Executing [s@from-sip-external:7] Log("SIP/sip.callcentric.com-00000012", "WARNING,"Rejecting unknown SIP connection from 199.87.144.75"") in new stack Do you recognize the IP address in this error message? Has it been...

If the students are using a "good old telephone" you may need to speak the time in alaw / ulaw rather than g722. Just a thought.

Double check the ports in use for sip at both ends of the connection. Wrong password might also be an indication of a port mismatch.

If you are running IncrediblePBX you shouldn’t be changing iptables because it is managed by IPBX.

How about posting the sanitized log output for a registration attempt.

Well I wish you luck but I'm out.

I really want to help you with this but if you don't/won't post the log output it's almost impossible to help as it could be a myriad of things causing the timeout. Reading and analyzing logs is necessary to diagnose this problem. If it was my problem I would be getting a pjsip trunk working on...

I find it hard to believe that the logs are empty. Do you have logging turned on with all options selected?

Here are some Voip.ms article I found about using PJSIP. https://wiki.voip.ms/article/FreePBX_(PJSIP) https://wiki.voip.ms/article/Asterisk_PJSIP https://community.freepbx.org/t/freepbx-w-voip-ms-using-tls/80603

What about Setting > Asterisk SIP Settings >SIP Settings [chan_pjsip] > TLS/SSL/SRTP Settings > SSL Method? And also the Transport section. Is everything correct there?

Well you are certainly at square one then. Start by making sure you are using the correct port for TLS at your end and at the voip.ms end. Then look at your From Domain and Match (Permit) settings and Contact User, From User and Authentication.

How do you know that if there’s nothing in the logs? Please post the log of a registration attempt.