Possible IAX Bug

[tRr]

I am having a problem using a voip.ms IAX connection. Outbound calls work fine. Inbound calls generate the following error message with the default Askozia configuration (this is with the latest version of Askozia, earlier versions had the same problem too):

Code:

asterisk[1360]: NOTICE[1403]: chan_iax2.c:10399 in socket_process: Host 64.120.22.242 failed to authenticate as voipms 

I have traced the problem to the text within the square brackets of iax.conf:

Code:

; voipms - incoming 
[subaccount_username] 
type=user 
auth=plaintext 
... 

By default Askozia places the IAX username of the account in the square brackets. This works fine for another provider of mine (and with CallWithUs when they offered IAX) but it seems like voip.ms only accepts "[voipms]" which I found in their configuration samples. When I changed the above from the automatically filled in IAX username to "voipms" incoming calls then worked as expected.

I don't know much about the nuts and bolts of Asterisk but since other providers work I'm thinking this is a voip.ms bug. I thought I would ask the experts just to make sure before I file a report with them.

[giovanni.v]

By default Askozia places the IAX username of the account in the square brackets. This works fine for another provider of mine (and with CallWithUs when they offered IAX) but it seems like voip.ms only accepts "[voipms]" which I found in their configuration samples. When I changed the above from the automatically filled in IAX username to "voipms" incoming calls then worked as expected.

I think the askozia configuration is correct. Usually for an incominq call/connection if a username  is provided asterisk will start to authenticate that call finding a user definition with a section name matching the provided username.
You already found the problem... your provider is using an arbitrary name in incoming calls instead of your real username, this is not forbidden but quite unusual for that setup.

Ask your provider to check if possible to change this. If not the only option (other than manual hacking) is to plan a patch providing an option to allow to configure a different incoming username.

[tRr]

Thanks giovanni.

I have used about 4 different IAX providers and this is the only one that does not work. I imagine this  also would cause issues if I were to have two IAX accounts with the same provider?

[giovanni.v]

I imagine this  also would cause issues if I were to have two IAX accounts with the same provider?

I agree.