I wouldn't mind using SIP with voip.ms if it worked right. I'll try it
again changing what needs changing, but for now, I'm not conducting any
secure communications, so I'll worry about it when things break.
On 5/27/2023 11:20 AM, aster...@phreaknet.org wrote:
IAX2 tends to work really well fo
IAX2 tends to work really well for trunking. Unlike SIP, it usually just
works, although it tends to be more a niche use case. For this reason,
IAX2 has long been a controversial technology; most people seem to
either love it or hate it. Obviously, you can guess what my bias is.
The only downsid
Thanks, Daryl. I fixed this before I saw this message by changing my
connectivity from SIP to IVR/IAX on voip.ms's Manage DID Numbers page.
I'll keep this one in my notes, though, should I ever do this again with
SIP.
On 5/26/2023 7:42 PM, Daryl Richards wrote:
On 2023-05-23 7:22 p.m., Steve
Sean,
I'll take that under advisement, but Doug swears by IAX, I tried it, it
worked, so until things break and break bad, I'll stick with that and
try the recommended remedy, now recommended by two people.
On 5/26/2023 8:08 PM, Sean Bright wrote:
On 5/26/2023 5:41 PM, Steve Matzura wrote:
On 5/26/2023 5:41 PM, Steve Matzura wrote:
> Doug from this list got me to change my connectivity to my DID provider
> from SIP to IAX, and bingo, it all just worked instantly.
Looking over your previous messages and the error you were receiving
(the one referring to extension 's') it looks like y
On 2023-05-23 7:22 p.m., Steve Matzura wrote:
And I think they're both small.
[May 23 18:34:12] NOTICE[46582]: res_pjsip_session.c:3968 new_invite:
voipms: Call (UDP:208.100.60.12:5060) to extension 's' rejected because
extension not found in context 'voipms-inbound'.
Steve,
In your voip.m
This was supposed to go to the list.
I am now thoroughly confused.
In the [voipms] stanza where endpoint is defined (type=endpoint),
everything points to voipms. But in the [yealink] stanzas, I tried
pointing everything
to Steve, one item at a time, then both of them, and nothing changed.
O
On 5/24/23 09:56, Steve Matzura wrote:
I don't understand your explanation because in the two files whose
contents I posted, there's nothing routed to anything called just 's'.
However, I've seen that in the error messages and it stumped me, too.
No 'start' either.
Steve,
Please make sure yo
Am Wed, May 24, 2023 at 09:40:18AM -0400 schrieb Steve Matzura:
>
> On 5/24/2023 7:49 AM, Stefan Tichy wrote:
> > Am Tue, May 23, 2023 at 07:22:22PM -0400 schrieb Steve Matzura:
> >
> > > 1. Still can't register my phone
> > > The username and password are correct. I don't know what else to try.
On 5/24/23 08:03, Steve Matzura wrote:
*** extensions.conf ***
[general]
[globals]
; Make sure to include inbound prior to outbound because the
_NXXNXX handler will match the incoming call and create a loop
include => voipms-inbound
include => voipms-outbound
[voipms-outbound]
exten
Am Tue, May 23, 2023 at 07:22:22PM -0400 schrieb Steve Matzura:
> 1. Still can't register my phone
> The username and password are correct. I don't know what else to try.
You can start a sip trace from the asterisk console.
pjsip set logger on
There should be a REGISTER from the phone, a Respon
On 5/23/23 19:22, Steve Matzura wrote:
voipms: Call (UDP:208.100.60.12:5060) to extension 's' rejected
because extension not found in context 'voipms-inbound
Steve,
Could we see your dialplan for voipms-inbound?
I'm using voip.ms as well, but have not converted from chan_sip yet. My
voip-m
12 matches
Mail list logo
