TIPS SIP URIs that work for me

[Halea]

You might have seen my posts regarding not being able to connect to Lenny viaSIP URI earlier today.
Well, I still can't, but my PBX seems to be able to place calls to the following SIP URIs.
I thought I would start a new thread and if you have more to add you are more than welcome!
SIP/[email protected]
SIP/[email protected]
SIP/[email protected]
SIP/[email protected]
SIP/[email protected]
sip/**[email protected]
sip/[email protected]
(If you have any suggestions about how to troubleshoot the Lenny URI please let me know, because I am completely out of ideas)

 

[ostridge]

the following SIP URIs

You can call [email protected] to check if audio and video works for your devices.
You can call [email protected] to test your microphone (echo test).

 

[Halea]

You can call [email protected] to check if audio and video works for your devices.
You can call [email protected] to test your microphone (echo test).

I tried both uris, neither worked! Just like with Lenny it keeps ringing for 20 to 30 seconds and stops. To make sure that the culprit is not the extension 53669 I just plugged in SIP/[email protected] and that worked instantly. I also tried the sip2sip.info uris on several different extensions which are now set to dial other uris (successfully), but as soon as they see sip2sip.info they never go beyond ringing.
I can trace route from the PBX console to sip2sip.info, DNS resolution works, pinging works. Not sure where else to look at.

 

[wardmundy]

@Halea: Try this one: sip/[email protected]

 

[Halea]

@Halea: Try this one: sip/[email protected]

Worked instantly! It was good to hear Lenny's voice again.

Edit: I've just got my public IPs scanned for blacklisting and apparently they are not. Besides I can access https://sip2sip.info which brings up an interactive web page in addition to pinging the ip address, etc. Further, sudo sngrep clearly shows an INVITE block going out, but apparently there is no answer. So, the only other explanation would be that my calls into UDP 5060 are blocked on sip2sip's firewall.

 

[wardmundy]

@Halea: Just curious if your PBX is a recent install of Incredible PBX 2020?? I built a new one yesterday on C@C and Lenny worked fine. Change the link above to cac3, and you can try it out as well.

 

[Halea]

@Halea: Just curious if your PBX is a recent install of Incredible PBX 2020?? I built a new one yesterday on C@C and Lenny worked fine. Change the link above to cac3, and you can try it out as well.

No this is a legacy Incredible PBX 12 with Asterisk 13 (the one with problems with sip2sip).
I will load Incredible PBX 2020 on a Pi and give a test drive to see if all those sip uri work.
Thank you for your help.

Edit: On my legacy PBX sip/[email protected] works flawlessly as well.

Unfortunately, now I have issues with my Pi and I can't get it going with Incredible PBX, but I think it is an SD socket issue as its contacts are a bit worn out.

 

[krzykat]

No this is a legacy Incredible PBX 12 with Asterisk 13 (the one with problems with sip2sip).
I will load Incredible PBX 2020 on a Pi and give a test drive to see if all those sip uri work.
Thank you for your help.

I have legacy ones working just fine. I swear I had that problem at one point, but don't recall exactly what it was. I think it was when I tried to call the directly with a custom call flow, but the when I placed it as a custom extension type, it worked perfect. I'll try to find notes later today to see if I find something on it.

 

[Halea]

I have legacy ones working just fine. I swear I had that problem at one point, but don't recall exactly what it was. I think it was when I tried to call the directly with a custom call flow, but the when I placed it as a custom extension type, it worked perfect. I'll try to find notes later today to see if I find something on it.

Thanks, I'd appreciate comparing notes on this issue. I am now convinced that sip2sip.info is blocking UDP#5060 initiated from my subnet.
Earlier, I configured linphone on my laptop and when I tried Lenny on sip2sip.info it failed the same way my PBX fails. But, when I connected my laptop to my cell phone hotspot and then tried the same, Lenny answered my call!
But since from my subnet I can reach a bunch of SIP URIs without problem I don't think that it's an issue with my IP numbers or my PBX.

 

[wardmundy]

You might want to check the VoIP Blacklist and make sure you don't have a winning number.

 

[ostridge]

Lenny on sip2sip.info it failed

I had the sip uri working fine before I installed the homebrew Lenny, though FWIW it occurs to me that I do have a working sip2sip trunk and a sip2sip CLI number.

 

[Halea]

You might want to check the VoIP Blacklist and make sure you don't have a winning number.

That would have made things easier! I checked a bunch of blacklists a few days back, and I did it again this morning, including voip blacklist. As far as I can tell my subnet is not blacklisted by any of them.

 

[wardmundy]

@Halea: Sounds like you can chalk it up to very old code that probably had a bug that got addressed down the road but never got documented.

 

[Halea]

@Halea: Sounds like you can chalk it up to very old code that probably had a bug that got addressed down the road but never got documented.

Well, I am putting this issue to rest anyway. Lenny is great but I didn't think it would take so much of my time and energy to hear his voice

 

[craig0]

Resurrecting this old thread - I have the exact same problem reaching Lenny on the sip2sip URI. The other URIs mentioned at the top of this thread work fine. This is on a fresh build of IncrediblePBX 2020 on Raspberry Pi 4 - Incredible PBX 2020 15.0.16.65.1