[Edited Message Follows]

This is the section where the 1998 needed to be changed to my node number:

[phone-iaxrpt]    ;;; Stanza is the context from iax.conf

exten => 42437,1,Answer

exten => 42437,n,Playback,rpt/node

exten => 42437,n,Playback,digits/1

exten => 42437,n,Playback,digits/9

exten => 42437,n,Playback,digits/9

exten => 42437,n,Playback,digits/8

exten => 42437,n,Set(CALLERID(num)=0)

exten => 42437,n,Rpt,1998|P|${CALLERID(name)} ;;; The "CallerID" from IAXRpt

I can show you the logs. Where will I find the log files in the dir structure?

I did some more troubleshooting and it seems to be related to the type setting.  When I change type=user to "friend" in the iax.conf [iaxrpt] stanza it will allow the app to connect using the iaxrpt user without throwing an error suggesting that there may be some issue with using the app to connect as a "user." Not sure the implications of that.

Example:

[iaxrpt]

user=iaxrpt

type=user friend

context=radio-iaxrpt

auth=md5

secret=  ; PASSWORD

host=dynamic

disallow=all

allow=ulaw

allow=gsm

transfer=no

[Edited Message Follows]

I think I figured it out. Two things:

1. DV Switch mobile app seems to only connect when using the [myphone-iaxrpt] stanza as the username. It will not connect to [iaxrpt]. It throws an invalid password or stanza. I verified the password so it is some other option.

2. I changed Line 60 of extensions.conf from 1998 to my node number. After doing that, I was able to connect without the "node 199..." disconnect error state.

This looks to be how they are configured and I am still getting the "node 199..." and disconnect.  Has anyone verified that these instructions work with the latest HamVOIP img? I am on the same LAN so I don't think ports would be an issue.

Thanks, I followed those instructions and now I am able to at least get the app to recognize the node. However, when I click connect in the app, I hear "node 199..." from the phone speaker and then it gets cut off and there is a tone.  It never actually completes the connection.  FYI, the node is a stock HamVOIP that I just re-flashed so everything is default except for the stanza I added to iax.conf per the wiki.

I have my own AllStarLink node and I would like to use DVSwitch Mobile on Android to access it.  It seems like this is a very powerful Android app but I can't seem to find documentation to do this. Is there a step-by-step document somewhere?  I just need to know what to change on the node and how to configure the mobile app to match.

Thanks for the response Brad !

I tried that and it stopped working altogether.  I looked in /opt/MMDV_Bridge/DVSwitch.ini and TX/RX are defined:

[DMR]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 31100                  ; Port to send AMBE TLV frames to (export)

RXPort = 31103                  ; Port to listen on (import)

Slot = 2                        ; Export slot

ExportTG = 0                    ; Which TG to export

TalkerAlias = Roger Nowhere Il. DVSWITCH

So I'm assuming that needs to be reversed in Analog_Bridge.ini ? - Tx goes to Rx and visa versa:

[AMBE_AUDIO]

address = 127.0.0.1                     ; IP address of xx_Bridge

txPort = 31103                          ; Transmit TLV frames to partner on this port

rxPort = 31100                          ; Listen for TLV frames from partner on this port

ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)

minTxTimeMS = 2500                      ; Minimum time in MS for hang delay (0-10000)

I'm getting traffic from the TG 91, but only if I momentarily click my PTT on the analog side whilst a 3rd party is speaking in the TG.  If the 3rd party in the TG stops an restarts their over, I don't resume receiving their traffic from the TG.

g

In the discussion of a issue with radioid.net missing some entries this weekend I posted a screenshot of a work in progress. So, since the cat is out of the bag...
This is a work in progress of the new web (HTML) client. We have no release date and the program has not even gone into beta test yet.
I'll post update info here when available.