[kitt1997]

Buongiorno a tutti!

Io ho sbloccato il modem flashando il firmware UNO, eseguendo sblocco.sh e abilitando qualche opzione in setup.sh, tra cui quella del VoIP per TIM.

Per connettermi ad internet uso una chiavetta 4G (non ho una connessione PPP) che il FW UNO ha riconosciuto all'istante e infatti funziona tutto a meraviglia.
L'unico problema è che non riesco a far registrare il VoIP nè di Messagenet nè di EhiWeb: ho impostato tutti i parametri correttamente ma se poi vado nei log mi esce questo:
[MMRVSIPIMPL::REGTERMOBJ]:E: profileTimerCb:439 - no matching IP address, the registration will be aborted

Qualcuno ha un'idea?
Grazie

[luckyluke22]

Devi rimettere vpi e vci a mano oltre alla pppoe

Grazie per le informazioni, purtroppo errore mio ho scritto ADSL senza specificare che oggi ho una connessione VDSL2
Spulciano in Internet per la VDSL TIM ho trovato questa configurazione
   username -> timadsl
   password -> timadsl
   VLAN ID -> 835
   Protocollo -> PPPoE Routed (definito come RFC2516)
   Incapsulamento -> PTM

Riuscite gentilmente a dirmi se torna?

Ringrazio anticipatamente

[FrancYescO]

Si

@kitt1997 credo tu debba cambiare l'ifname nei file di config di mmpbxd

Giusto per curiosità, qual è il modello di chiavetta 3G che stai usando?

[kitt1997]

@FrancYescO
Anche io credevo che fosse quella la causa e infatti ho impostato da uci mmpbxrvsipnet.sip_net.interface='wwan' (prima era impostato su wan). Ho riavviato tutto ma continua a dare quel messaggio.
Sono andato a vedere nel file di config ed effettivamente lo ha impostato su wwan:

Codice: [Seleziona]

config network 'sip_net'
      […]
      option interface 'wwan'

La chiavetta è una ZTE MF831 della 1&1.

[LuKePicci]

Dipende dalla chiavetta, ma a me funzionava correttamente mettendoci wwan_ppp (essando la mia chiavetta connessa in ppp).

[kitt1997]

@LuKePicci
La mia chiavetta funziona da router in pratica: ha due indirizzi ip (uno locale e uno del gestore) e assegna un indirizzo ip locale al Technicolor, tipo 192.168.137.153. È come avere un router in cascata per intenderci.
Adesso ho provato anche wwan_ppp e wwan_eth ma niente.
Non è nemmeno un problema di NAT o firewall perchè ho provato con un client VoIP dal PC e mi funzionano entrambi gli account.

[LuKePicci]

Ho presente il tipo di funzionamento, ma non so come si chiama l'interfaccia da cui risulta connesso. Prova a dare una occhiata all'output di ifconfig. Hai provato con wwan_4?

[kitt1997]

@LuKePicci
In ifconfig c'è effettivamente usb0 che mi era sfuggito (mentre non c'è wwan), ma non funziona neanche con quello. Strano davvero.
Nemmeno wwan_4. Ho provato wwan0, wwan_eth_dhcp … nulla.

[LuKePicci]

wwan non c'è mai, alla fine si chiamano sempre wwan_ppp/wwan_4/wwan_6, a prescindere dal nome dell'interfaccia fisica che c'è sotto (usb0 nel tuo caso). Prova a tenere impostata wwan_4 che credo sia quella corretta, connetti la chiavetta e dai "ifconfig -a"

[larsen64it]

Da openwrt

Codice: [Seleziona]

Some modem sticks provide an usb-ethernet-device (e.g. Huawei “HiLink” - device numbers with 'h', but also other manufacturers like ZTE
 has such products MF823, MF831, …) In that case you should install usb-modeswitch package and follow usb tethering tutorial. Tethering will in
 most cases add an additional NAT layer. If you prefer to let OpenWRT care about dialing in, routing, NATting, firewalling or if your provider
assigns you an external IPv4 (which is most useful for setups, that need port forwarding), you will most likely want to set (“modeswitch”) your
3g/4g modem to act as a serial device.https://openwrt.org/docs/guide-user/network/wan/wwan/3gdongle
L'interfaccia dovrebbe essere wan
in /etc/config/network

Codice: [Seleziona]

config interface 'wan'
option ifname 'usb0'
option proto 'dhcp'

[kitt1997]

@LuKePicci
Se imposto wwan_4 e do ifconfig -a  mi escono delle nuove interfacce (tunnel ipv6, dsl0, atm0, ptm0 …) ma niente che si riferisca alla connessione wan se non usb0.

@larsen64it
Sono riuscito a forzare la chiavetta ad avviarsi come se fosse un modem seriale e quindi a far fare la connessione PPP al Technicolor ed effettivamente il VoIP mi funziona. 
Per i futuri lettori questo è il sito dove ho preso lo spunto: https://technicalexperiments.wordpress.com/2015/10/30/zte-mf831-for-use-with-openwrt-serial-modem-instead-of-cdc_ether

Chiaramente c'è lo svantaggio di perdere l'interfaccia web della chiavetta stessa e forse anche una maggiore lentezza del protocollo PPP (?), come dice il sito di OpenWrt. Almeno però il VoIP funziona...

Grazie a tutti!

[LuKePicci]

@larsen64it la pagina che hai trovato su openwrt riguardo la wwan si riferisce al pacchetto di gestione nativo della distribuzione, quello di technicolor è diverso, se guardi nei file (da qualche parte in /usr/lib/lua mi pare) c'è lo script di mobiled che definisce quale interfaccia usare in base al tipo di chiavetta.

@kitt1997 l'interfaccia wwan usata è nascosta, viene creata al volo in fase di configurazione della chiavetta, vale lo stesso per wwan_ppp e wwan_4, però se con la prima tutto funziona allora mi viene il dubbio che la differenza stia nel fatto che col primo metodo l'ip pubblico è assegnato ad una sua stessa interfaccia. Pur sapendo che il technicolor se opportunamente configurato non crea problemi di NAT al VoIP fatto da client in LAN, non ho mai provato ad usare il client del technicolor dietro un NAT. Se ti capita di fare altre prove e riesci a farmi avere un log completo di mmpbx insieme ad una cattura tcpdump su usp0 vorrei controllare una cosa su cui ho un sospetto.

[larsen64it]

Se usa usb0 all'ora è usato come "adattatore eth" e il TG789 è come fosse dietro ad un router. Resta da capire se deve essere usata un interfaccia wan o wwan.
In /usr/lib/lua/mobiled/detector.lua, bisognerebbe vedere se sono presenti i vid e pid e casomai aggiungerli e vedere l'effetto che fa.

Codice: [Seleziona]

local usb_descriptors = {
{
plugin = "libwebapi",
device_identifiers = {
-- ZTE MF730E
{
vid = "19d2",
pid = "1405"
},
-- ZTE MF823
{
vid = "19d2",
pid = "1403"
},
{
vid = "12d1",
pid = "157f"
},
{
vid = "12d1",
pid = "1590"
},
{
vid = "12d1",
pid = "14db"
}
}
},

[kitt1997]

@LuKePicci
Se uso la chiavetta come modem, viene creata wan_ppp visibile da ifconfig a cui è assegnato l'ip pubblico. Se uso la chiavetta normalmente, in ifconfig c'è usb0 che ha ip locale assegnato dalla chiavetta.
Questo è il log di un avvio di mmpbx, il tcpdump te lo mando in pm:

Codice: [Seleziona]

Thu Oct 24 10:53:22 2019 daemon.info transformer[3674]: async run: /etc/init.d/mmpbxd restart
Thu Oct 24 10:53:24 2019 user.info root: Mmpbx stopping, mmpbx.state=STOPPING
Thu Oct 24 10:53:24 2019 user.info root: Mmpbx service_stop voice=NA@init_stop
Thu Oct 24 10:53:24 2019 user.info root: Mmpbx service_stop done
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on broadband:red
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/broadband:red with action none
Thu Oct 24 10:53:25 2019 daemon.warn ledfw[1478]: Could not open /sys/class/leds/broadband:red/trigger
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on broadband:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/broadband:green with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on internet:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/internet:green with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on internet:red
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/internet:red with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on iptv:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/iptv:green with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on iptv:red
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/iptv:red with action none
Thu Oct 24 10:53:25 2019 daemon.warn ledfw[1478]: Could not open /sys/class/leds/iptv:red/trigger
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on ethernet:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/ethernet:green with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on wireless:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/wireless:green with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on wireless:red
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/wireless:red with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on wireless_5g:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/wireless_5g:green with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on wireless_5g:red
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/wireless_5g:red with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on wps:orange
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/wps:orange with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on wps:red
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/wps:red with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on wps:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/wps:green with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on dect:red
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/dect:red with action none
Thu Oct 24 10:53:25 2019 daemon.warn ledfw[1478]: Could not open /sys/class/leds/dect:red/trigger
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on dect:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/dect:green with action none
Thu Oct 24 10:53:25 2019 daemon.warn ledfw[1478]: Could not open /sys/class/leds/dect:green/trigger
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on dect:orange
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/dect:orange with action none
Thu Oct 24 10:53:25 2019 daemon.warn ledfw[1478]: Could not open /sys/class/leds/dect:orange/trigger
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on voip:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/voip:green with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on power:orange
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/power:orange with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on power:red
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/power:red with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 255
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on power:blue
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/power:blue with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: applying action on power:green
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: writing to /sys/class/leds/power:green with action none
Thu Oct 24 10:53:25 2019 daemon.debug ledfw[1478]: setting brightness to 0
Thu Oct 24 10:53:26 2019 user.info root: Mmpbx stopped, mmpbx.state=NAstopped
Thu Oct 24 10:53:27 2019 user.info root: Mmpbx starting mmpbx.state=STARTING
Thu Oct 24 10:53:28 2019 kern.warn kernel: [78051.741000] Endpoint: endpoint_init entry
Thu Oct 24 10:53:28 2019 kern.warn kernel: [78051.749000] Endpoint: endpoint_init COMPLETED
Thu Oct 24 10:53:28 2019 kern.warn kernel: [78052.052000] mmConnKrnlBrcm: INIT: num_rtpsock_ctx = 42
Thu Oct 24 10:53:28 2019 kern.warn kernel: [78052.056000] mmConnKrnlBrcm: INIT: COMPLETED
Thu Oct 24 10:53:30 2019 kern.info kernel: [78054.167000] xt_CT: No such helper "SIP"
Thu Oct 24 10:53:30 2019 daemon.err fw-ext: Error adding CT helper SIP for udp ( --dport 5060) in helper_binds
Thu Oct 24 10:53:30 2019 kern.info kernel: [78054.218000] xt_CT: No such helper "SIP"
Thu Oct 24 10:53:30 2019 daemon.err fw-ext: Error adding CT helper SIP for udp ( --dport 5060) in helper_binds
Thu Oct 24 10:53:34 2019 user.info root: the 2 values of max contact do not exist!
Thu Oct 24 10:53:34 2019 user.debug mmpbxd[19380]: [MEMM] Info: Pooldescr [memm_pooldesc] reallocated to increase its size (107 elements)
Thu Oct 24 10:53:34 2019 user.debug mmpbxd[19380]: [MMAPP]         :E: mmAppSetPriority:1816 - Configured priority value 0 or negative, priority not modified for mmapp
Thu Oct 24 10:53:34 2019 user.debug mmpbxd[19380]: [MMAPP]         :E: mmAppSetRefMediaFileGenPriority:1879 - Configured priority value 0 or negative, priority not modified for refmediafilegen
Thu Oct 24 10:53:34 2019 user.debug mmpbxd[19380]: [MMAPP]         :E: mmAppSetUbusPriority:1851 - Configured priority value 0 or negative, priority not modified for mmubus
Thu Oct 24 10:53:34 2019 user.debug mmpbxd[19380]: [MMUCI]         :E: mmUciCommonAllocateContext:248 - Error loading the UCI config from file for mmpbxbrcmsi3226x: UCI_ERR_NOTFOUND
Thu Oct 24 10:53:34 2019 user.debug mmpbxd[19380]: [MMUCI]         :E: mmUciCommonAllocateContext:248 - Error loading the UCI config from file for mmpbxbrcmsi3217x: UCI_ERR_NOTFOUND
Thu Oct 24 10:53:34 2019 kern.info kernel: [78058.191000] endptInitThreadFunc: Thread voice_EPINIT awakened, task:INIT
Thu Oct 24 10:53:34 2019 kern.warn kernel: [78058.198000] BOS: Enter bosInit
Thu Oct 24 10:53:34 2019 kern.warn kernel: [78058.201000] BOS: Exit bosInit
Thu Oct 24 10:53:34 2019 kern.warn kernel: [78058.204000] bosTaskCreate: Task Name: aoRT Binding 0x8701b858
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.403000] ******* DSP: Found BCM63268 *******
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.407000] ******* DSP: In PCM Mode *******
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.411000] ******* DSP: PCM running in 16 bit mode *******
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.417000] gInterruptCounter     = 0xC481E294
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.421000] gInterruptErrors      = 0xC481E290
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.426000] gNextRxDesc           = 0xC481E3C8
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.431000] gNextTxDesc           = 0xC481E3CC
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.435000] gDectTestMode         = 0xc481e3dc
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.440000] dectBuffStart         = 0xc481e3d0
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.445000] gDectRxOutOfSyncCounter = 0xc481e3f0
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.449000] gDectTxOutOfSyncCounter = 0xc481e3f4
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.454000] 32 ms ECAN tail-length
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.458000] *** gStartRxDesc[0] = 0xA73F9000
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.462000] *** gBufferSizeBytes = 640
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.466000] *** gStartTxDesc[0] = 0xA73F97D0
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.471000] halPcmInit 367 nextTxDesc = 0xA73F97D0
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.476000] halPcmInit 367 nextTxDesc = 0xA73F97D8
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.481000] halPcmInit 371 Ownership for TX desc not set. Use this buffer.
Thu Oct 24 10:53:35 2019 kern.warn kernel: [78058.489000] bosTaskCreate: Task Name: HTSK Binding 0x84030678
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.368000] boardHalInit completed
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.373000] bosTaskCreate: Task Name: HRTBEAT Binding 0x8f8344d8
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.379000] bosTaskCreate: Task Name: VRGDISP Binding 0x8f8e0068
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.385000] bosTaskCreate: Task Name: HCAS Binding 0x87b4f848
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.399000] bosTaskCreate: Task Name: ISTW Binding 0x870c6608
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.405000] DSP: Interrupt Ids
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.408000] ---------------
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.410000] InterruptId/Location      = 42/HIGH
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.415000]
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.415000] DSP: Interrupt Masks
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.420000] ---------------
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.423000] IrqMask                   = 0x00000100
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.428000] IrqMaskLow                = 0x838066A1
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.433000] IrqMask1                  = 0x00000400
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.438000] IrqMaskLow1               = 0x00000000
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.443000]
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.443000] DSP: Interrupt Status
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.448000] -----------------
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.451000] IrqStatus                 = 0x00100000
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.456000] IrqStatusLow              = 0x00038100
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.461000] IrqStatus1                = 0x00100000
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78060.466000] IrqStatusLow1             = 0x00038100
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78061.134000] EndpointInit completed
Thu Oct 24 10:53:37 2019 kern.warn kernel: [78061.137000] dgasp: kerSysRegisterDyingGaspHandler: endpoint registered
Thu Oct 24 10:53:37 2019 user.debug mmpbxd[19380]: [MMBRCMFXS]     :C: switchRelay:982 - Error switching relay, returned error: 8
Thu Oct 24 10:53:37 2019 user.debug mmpbxd[19380]: [MMBRCMFXS]     :C: switchRelay:982 - Error switching relay, returned error: 8
Thu Oct 24 10:53:37 2019 user.debug mmpbxd[19380]: [REFMEDIAFILEGENIMPL]:E: refMediaFileGenImplInit:225 - Configured priority value 0 or negative, priority not modifiedfor mmpbxrefmediafilegen
Thu Oct 24 10:53:38 2019 user.debug mmpbxd[19380]: [MMRVSIPIMPL]   :E: mmNetImplRvSipSetMtfPriority:145 - Configured priority value 0 or negative, priority not modified for mtf thread
Thu Oct 24 10:53:38 2019 user.debug mmpbxd[19380]: [MMUBUS]        :E: parseTriggerFd:172 - Ubus invoke went wrong
Thu Oct 24 10:53:38 2019 user.debug mmpbxd[19380]: [MMUBUS]        :E: mmUbusInvokeSync:514 - invokeSync got response with return value 4
Thu Oct 24 10:53:38 2019 user.debug mmpbxd[19380]: [MMPBX]         :C: mmAppBusGetCurrentIp:765 - Failed to call network.interface status
Thu Oct 24 10:53:38 2019 user.debug mmpbxd[19380]: [MMPBX]         :E: loadAudioNotificationConfig:2614 - Notification does not specify any event_descriptions
Thu Oct 24 10:53:38 2019 user.debug mmpbxd[19380]: [MMPBX]         :E: loadAudioNotificationConfig:2614 - Notification does not specify any event_descriptions
Thu Oct 24 10:53:38 2019 user.debug mmpbxd[19380]: [MMPBX]         :E: loadAudioNotificationConfig:2614 - Notification does not specify any event_descriptions
Thu Oct 24 10:53:38 2019 user.debug mmpbxd[19380]: [MMRVSIPIMPL::REGTERMOBJ]:E: profileTimerCb:439 - no matching IP address, the registration will be aborted
Thu Oct 24 10:53:54 2019 user.info root: Mmpbx is started, mmpbx.state=RUNNING !
@larsen64it
Nel mio /usr/lib/lua/mobiled/detector.lua ci sono li stessi valori che hai postato. La mia chiavetta comunque ha vid=19d2 e pid=1405.

[larsen64it]

Con usb0 sarebbe da vedere anche il comando route