I have some additional information, using wireshark and the IAX2 RFC I
walked through the handshaking of the call. I did three different calls,
RSA Authentication WITHOUT forcing encryption, RSA Authentication WITH
forcing encryption, and Clear Text Authentication WITH forcing
encryption.
Any ideas? Still hoping..
On Sun, Apr 6, 2014 at 12:03 AM, Elliott W dig...@private-address.infowrote:
I have.
On the receiving side I had gotten:
[2014-04-05 23:28:12] WARNING[1832] chan_iax2.c: Rejected connect attempt.
No secret present while force encrypt enabled.
I had no secret
I have.
On the receiving side I had gotten:
[2014-04-05 23:28:12] WARNING[1832] chan_iax2.c: Rejected connect attempt.
No secret present while force encrypt enabled.
I had no secret because I was using RSA authentication and didn't think I
needed it, so I added EXACTLY the same line on both
Ok, I think I am 90%+ there.
Note: the configuration or status is the same on both sides unless
otherwise noted.
I am using RSA keys for authentication and the calls are coming through as
authenticated so I'm sure that part works.
The peer shows the (E) next to the status in Asterisk Info for
Wireshark.
On Fri, Apr 4, 2014 at 11:13 AM, Elliott W dig...@private-address.infowrote:
Ok, I think I am 90%+ there.
Note: the configuration or status is the same on both sides unless
otherwise noted.
I am using RSA keys for authentication and the calls are coming through as
That answered my question as to whether it WAS encrypted, I think, and the
answer is no, the credentials are but all the rest is not. That just
leaves the question of what I need to do to get it encrypted..
Thanks.
On Fri, Apr 4, 2014 at 12:59 PM, Steve Totaro
stot...@totarotechnologies.com
Have you enabled IAX2 debugging and tried some test calls?
Thanks,
Steve T
On Fri, Apr 4, 2014 at 6:59 PM, Elliott W dig...@private-address.infowrote:
That answered my question as to whether it WAS encrypted, I think, and the
answer is no, the credentials are but all the rest is not. That
