IAX clients disconnect immediately after connection message

Hi,

I have a new installation of ASL3 (node 63002) and am trying to get IAX working so I can monitor using either Zoiper or DVSwitch on my cellphone. I can connect to the server using either client, and dial the node (using number 63002). I get the usual message “Connected to node 63002”, but the the call drops immediately. I was expecting (certainly with DVSwitch) that the call would result in the PTT button on the cellphone being usable, and that I’d get audio from the node.

My iax.conf stanza:

[M0DWK]                      ; Connect from iax client (Zoiper...)
type = friend                    ; Notice type here is friend <--------------
context = iax-client             ; Context to jump to in extensions.conf
auth = md5
secret = ******
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = slin
transfer = no
codecpriority = Caller

and my extensions.conf stanza:

[iax-client]                            ; for IAX VoIP clients.
exten => ${NODE},1,Ringing()
        same => n,Wait(1)
        same => n,Answer()
        same => n,Set(CALLSIGN=${CALLERID(name)})
        same => n,NoOp(Caller ID name is ${CALLSIGN})
        same => n,NoOp(Caller ID number is ${CALLERID(number)})
        same => n,GotoIf(${ISNULL(${CALLSIGN})}?hangit)
        same => n,Playback(rpt/connected-to&rpt/node)
        same => n,SayDigits(${NODE})
        same => n,rpt(${NODE}|P|${CALLSIGN}-P)
        same => n(hangit),NoOp(No Caller ID Name)
        same => n,Playback(connection-failed)
        same => n,Wait(1)
        same => n,Hangup

which I believe are fairly stock. In DVSwitch I set the server to <my.server.url.net>, the username to M0DWK, password as set, callerID to M0DWK, caller number to 0, and node to 63002.

In the asterisk messages.log I observe:

[2024-12-23 23:31:37.872] WARNING[10656] chan_iax2.c: Call on IAX2/M0DWK-4584 is already up, can't start on it
[2024-12-23 23:31:45.598] NOTICE[11054][C-00000011] app_rpt.c: Radio Channel Busy.

I’m wondering if this is an issue in rpt.conf as a result. Can anyone point me in the right direction?

Many thanks,

Chris M0DWK

requirecalltoken = no

Thanks Mike. No dice, sadly. I still get the same immediate disconnect after the voice message “Connected to node 63002”.

You do need that line in any case.

Some leads to check…

Be careful of any special characters in the secret. In fact, till you get it working, use 12345.

The error appears to show that it was connected and not hungup.
As a friend, it will only allow one connect, just like a node.

Sever address - ip:port
ie 192.168.1.1:4569 (inside your nat) WANIP:port on the outside…

Yes, so DVSwitch definitely registers with the server, just cannot (maintain a) connect(ion). I’ve checked and double checked the URL and password characters as above, and I’d be surprised if it were possible for DVSwitch to connect if they weren’t"T right (as evidenced by mistyping my password yesterday).

If it’s possible to only have one “friend” per node, might it be that the radio is blocking the connection?

Apologies, though I’m an experienced programmer and Linux sysad, I’m an asterisk newbie!

Regards,

Chris

[edit] @Mike following your comment

As a friend, it will only allow one connect, just like a node

I realised that as I’d connected my node to a hub node already, maybe this was blocking my DVSwitch Android device from connecting. This turns out to be true, as if I disconnect from the hub, I can connect with my Android device successfully. I guess I need to work out how to accept multiple connections, then!

Thanks for your helpful comments.

You keep comparing a dvswitch connection which I have no idea of what type.
IAX or USRP , if it is not an issue, stop confusing the issue with it.
It is impossible to know where you are with this.

Not one friend. A connection of same ‘user’ who is friend. And the error may only be a result of something else that is not right. But it kinda speaks for itself.
Is your dvs iax connection using the same user ?

Back to the initial post where I am less confused…

This is what I use with zopier.
I make a extension in iax

[5023] ;iphone 8P
deny=0.0.0.0/0.0.0.0
permit=73.115.0.0/16
permit=192.168.1.0/24
type=friend
username=5023
secret=xxxxxx
host=dynamic
context=radio-control
callerid=ip8p<5023>
disallow = all
allow=ulaw
transfer = yes
dial=iax2/5023
requirecalltoken = no

Once this is registered, I dial where it is to be received by extensions.conf and routed.

in the listed context (yours is likely different, adjust)
to dial other phones
exten => _50[012]X,1,Dial(sip/${EXTEN},17) ;dial ext/functions on this box
exten => _50[012]X,n,VoiceMail(5000) ; common vm
exten => _50[012]X,n,Hangup

To dial the node, dial the node number. Received and acted with this

exten => 48233,1,Answer
exten => 48233,n,Wait(2)
exten => 48233,n,Playback(rpt/node)
exten => 48233,n,SayDigits(48233)
exten => 48233,n,Rpt(48233|P)

This is a phone connection. Phone protocol applies. “P”

With iaxrpt I do not use iax client example for I am the only iax admin/user to my nodes.
[iaxrpt]
type = user
context = iaxrpt
auth = md5
secret = xxxxxx
host = dynamic
disallow = all
allow = ulaw
;allow = adpcm
;allow = gsm
transfer = no
requirecalltoken = no

and it is routed in extensions.conf
[iaxrpt]
exten => 48233,1,rpt(48233|X)

The “X” designation along with type ‘user’ somewhat bypasses some security measures and the connection is somewhat transparent. Perfect for admin’ing my nodes without visibility. Use a strong password.

when you use iax-clent, you ‘look like’ a node of username. Perfect for outside iax users that you have to manage.

https://wiki.allstarlink.org/wiki/Setup/Download_IAXRpt

You keep comparing a dvswitch connection which I have no idea of what type.
IAX or USRP , if it is not an issue, stop confusing the issue with it.

Fair. I’ll quit harping on about it. FWIW, it’s IAX.

Is your dvs iax connection using the same user ?

Bingo! I changed the username and now I can connect successfully. Thanks for picking this up. My Christmas reading is going to be the Asterisk manual, I guess…

Many thanks for the help, 73, and a very happy Christmas and New Year to you.

Chris, M0DWK

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.