I've had the 'phantom' node PTT issue when connecting from DVSwitch/iaxrpt on Android. It took some digging to realize there are two different suggested solutions to apply to the context(s) in extensions.conf. One says to apply: exten=<node#>,1,rpt, <node#>|X - which does not effect the desired solution (for DVSwitch/iaxrpt on Android) The other says to apply: exten=<node#>,1,rpt, <node#>|P - which DOES effect the desired solution I'm thinking you cannot have both an |X and a |P related statement in the same context... so I'd have to establish different contexts for different types of VoIP app users? and of course accommodate them in iax.conf... Is or can this be documented comprehensively? And please - if a change is to be edited in some file - indicate which file... put the some 'x' statement in the wrong file and the node breaks or statement is useless... generates more back and forth clarifications. ----------- Further - interesting/compelling, would be great to have, the mention of perhaps having the connected node(s) announce the "callerID" of the connecting user - *great* - but not (yet?) implemented? If it IS implemented - more detail please! exten=<node#>,1,rpt, <node#>|P|${CALLERID(name)} Thanks!!