What do I need to do to get voicemail working? Install vvm?
I read all the docs, poked around, but sadly I still could not figure it
out.
I see some menu entries in SXMO about voicemail, is this something that
should 'just work'? If so, I may have buggered it up somehow.
Cheers,
TRS-80
Should just install vvmd (its an alpine package), then there's a vvmd
config menu which is close to mmsd config menu.
More details:
https://gitlab.com/kop316/vvmd
Config file is ~/.vvm/modemmanager/vvm, which is what our menu edits for
you.
On Thu, Nov 10, 2022 at 03:43:03PM -0500, TRS-80 wrote:
>What do I need to do to get voicemail working? Install vvm?>>I read all the docs, poked around, but sadly I still could not figure it>out.>>I see some menu entries in SXMO about voicemail, is this something that>should 'just work'? If so, I may have buggered it up somehow.>>Cheers,>TRS-80
--
sic dicit magister P
https://phartman.sites.luc.edu/
GPG keyID 0xE0DBD3D6 (CAE6 3A6F 755F 7BC3 36CA 330D B3E6 39C6 E0DB D3D6)
"Hartman, Peter" <phartman@luc.edu> writes:
> Should just install vvmd (its an alpine package), then there's a vvmd > config menu which is close to mmsd config menu.>> More details:> https://gitlab.com/kop316/vvmd>> Config file is ~/.vvm/modemmanager/vvm, which is what our menu edits for > you.
Thanks for the fast reply.
It looks like I have vvmd running already, actually. I tried to install
it with 'sudo apk add vvmd' but nothing happened. And I can see it
there running in 'top'.
So, it must be something else. I don't think I have MMS working quite
right, either (not sure if related?).
Where/how are we supposed to be able to listen to the messages? If I am
remembering correctly, on Mobian, there was a graphical Visual Voicemail
client/application, in addition to the daemon. Not sure how this is
supposed to work in SXMO? Maybe I am simply mis-understanding
something.
Cheers,
TRS-80
Our code (sxmo_vvms.sh) just converts it into an sms with an audio file
attached to it, so once you have the vvm config file setup it should all
work.
On Thu, Nov 10, 2022 at 05:29:57PM -0500, TRS-80 wrote:
>"Hartman, Peter" <phartman@luc.edu> writes:>>> Should just install vvmd (its an alpine package), then there's a vvmd>> config menu which is close to mmsd config menu.>>>> More details:>> https://gitlab.com/kop316/vvmd>>>> Config file is ~/.vvm/modemmanager/vvm, which is what our menu edits for>> you.>>Thanks for the fast reply.>>It looks like I have vvmd running already, actually. I tried to install>it with 'sudo apk add vvmd' but nothing happened. And I can see it>there running in 'top'.>>So, it must be something else. I don't think I have MMS working quite>right, either (not sure if related?).>>Where/how are we supposed to be able to listen to the messages? If I am>remembering correctly, on Mobian, there was a graphical Visual Voicemail>client/application, in addition to the daemon. Not sure how this is>supposed to work in SXMO? Maybe I am simply mis-understanding>something.>>Cheers,>TRS-80>
--
sic dicit magister P
https://phartman.sites.luc.edu/
GPG keyID 0xE0DBD3D6 (CAE6 3A6F 755F 7BC3 36CA 330D B3E6 39C6 E0DB D3D6)
It appears we got off list somehow. For the benefit of posterity, I've
replied to the last on-list message, but below I quote the message I
received off-list:
"Hartman, Peter" <phartman@luc.edu> writes:
> On Fri, Nov 11, 2022 at 08:00:15AM -0500, TRS-80 wrote:>>"Hartman, Peter" <phartman@luc.edu> writes:>>>>> Our code (sxmo_vvms.sh) just converts it into an sms with an audio file>>> attached to it, so once you have the vvm config file setup it should all>>> work.>>>>Where would those be located, and/or how to listen to them? Some menu>>option? I don't see anything.>>>>What I see are some SMS(?) messages that look like:>>>>Received SMS from 127 at 2022-10-27T09:01:02-0400:>>//VVM:STATUS:st=R;rc=0;srv=e5.vvm.mstore.msg.t-mobile.com;ipt=148;u=XXXXXXXXXXX;pw=YYYYYYYYYYY;lang=1|2|3|4;g_len=180;vs_len=10;pw_len=4-9>>>>Received SMS from 127 at 2022-11-04T17:56:00-0400:>>//VVM:SYNC:ev=NM;id=791;c=11;t=v;s=ZZZZZZZZZZZ;dt=04/11/2022 14:55 -0700;l=24>>>>...where XXX... is my phone number and I suppose YYY... is my>>'password', and ZZZ... is the other number(?).>>>>I mentioned previously that I am not sure MMS are working properly,>>maybe that is related (but no idea really)?> I'm not sure if you need mms working in order to get vvm working. Could > be, I haven't tested.>> But you *will* need to edit ~/.vvm/modemmanager/vvm (the config file) to > enter the relevant info for your carrier. REMEMBER: You have to bring > vvmd down BEFORE you edit this file, otherwise it'll overwrite it.>> You can find details on the vvm config stuff here:>> https://gitlab.com/kop316/vvmd>> For instance, I use Mint Mobile (a variant on T-Mobile):>> [Modem Manager]> VVMEnabled=true> VVMType=cvvm> VVMDestinationNumber=127> DefaultModemNumber=+1773XXXXXXX> CarrierPrefix=//VVM> ProvisionStatus=2> IMSI=XXXXX>> [Settings]> MailboxHostname=e4.vvm.mstore.msg.t-mobile.com> MailboxPort=148> MailboxUsername=XXXX> MailboxPassword=XXXX> MailboxActive=true> MailboxURI=imaps://e3.vvm.mstore.msg.t-mobile.com/INBOX> MailboxAuth=AUTH=PLAIN> UseMailboxInterface=false> MailboxStartTLS=false> MailboxLanguage=1|2|3|4> GreetingLength=180> VSLength=10> TUIPasswordLength=4-9> MailboxVVMType=cvvm> MailboxLegacyTLS=false>
Yes I already found the VVM config file located at
~/.vvm/modemmanager/vvm. Mine also looks very similar to yours (I am on
MetroPCS which is also owned by T-Mobile in US):
[Modem Manager]
VVMEnabled=true
VVMType=cvvm
VVMDestinationNumber=127
CarrierPrefix=//VVM
DefaultModemNumber=NULL
ProvisionStatus=2
IMSI=XXXXXXXXXXXXXXX
[Settings]
MailboxHostname=vvm.mstore.msg.t-mobile.com
MailboxPort=148
MailboxUsername=XXXXXXXXXXX
MailboxPassword=XXXXXXXXXXX
MailboxActive=true
MailboxURI=imaps://vvm.mstore.msg.t-mobile.com/INBOX
MailboxAuth=AUTH=PLAIN
UseMailboxInterface=false
MailboxStartTLS=false
MailboxLanguage=1|2|3|4
GreetingLength=180
VSLength=10
TUIPasswordLength=4-9
MailboxVVMType=cvvm
Near as I can tell (from looking at messages I receive from '127') this
seems to be the correct info(?).
> A lot of that was auto-populated already so I only had to change a few > things.
Like you, mine was already auto-populated (IIRC).
But I'm very curious what changes you might have made? :)
> Once that is done, vvm messages will come in as regular messages as far > as sxmo is concerned.>> vvmd has good debug log and kopi is pretty prompt about helping debug, > but you can also send the debug here and I can look at it (or in irc)
Which debug log are we talking about? I see
~/.local/share/sxmo/modem/modemlog.tsv, is there another one specific to
vvm? I looked in /var/log and checked vvm docs, but not finding it yet.
Cheers,
TRS-80
On Fri, Nov 11, 2022 at 09:53:18AM -0500, TRS-80 wrote:
>It appears we got off list somehow. For the benefit of posterity, I've>replied to the last on-list message, but below I quote the message I>received off-list:>>"Hartman, Peter" <phartman@luc.edu> writes:>> On Fri, Nov 11, 2022 at 08:00:15AM -0500, TRS-80 wrote:>>>"Hartman, Peter" <phartman@luc.edu> writes:>>>>>>> Our code (sxmo_vvms.sh) just converts it into an sms with an audio file>>>> attached to it, so once you have the vvm config file setup it should all>>>> work.>>>>>>Where would those be located, and/or how to listen to them? Some menu>>>option? I don't see anything.>>>>>>What I see are some SMS(?) messages that look like:>>>>>>Received SMS from 127 at 2022-10-27T09:01:02-0400:>>>//VVM:STATUS:st=R;rc=0;srv=e5.vvm.mstore.msg.t-mobile.com;ipt=148;u=XXXXXXXXXXX;pw=YYYYYYYYYYY;lang=1|2|3|4;g_len=180;vs_len=10;pw_len=4-9>>>>>>Received SMS from 127 at 2022-11-04T17:56:00-0400:>>>//VVM:SYNC:ev=NM;id=791;c=11;t=v;s=ZZZZZZZZZZZ;dt=04/11/2022 14:55 -0700;l=24>>>>>>...where XXX... is my phone number and I suppose YYY... is my>>>'password', and ZZZ... is the other number(?).>>>>>>I mentioned previously that I am not sure MMS are working properly,>>>maybe that is related (but no idea really)?>>> I'm not sure if you need mms working in order to get vvm working. Could>> be, I haven't tested.>>>> But you *will* need to edit ~/.vvm/modemmanager/vvm (the config file) to>> enter the relevant info for your carrier. REMEMBER: You have to bring>> vvmd down BEFORE you edit this file, otherwise it'll overwrite it.>>>> You can find details on the vvm config stuff here:>>>> https://gitlab.com/kop316/vvmd>>>> For instance, I use Mint Mobile (a variant on T-Mobile):>>>> [Modem Manager]>> VVMEnabled=true>> VVMType=cvvm>> VVMDestinationNumber=127>> DefaultModemNumber=+1773XXXXXXX>> CarrierPrefix=//VVM>> ProvisionStatus=2>> IMSI=XXXXX>>>> [Settings]>> MailboxHostname=e4.vvm.mstore.msg.t-mobile.com>> MailboxPort=148>> MailboxUsername=XXXX>> MailboxPassword=XXXX>> MailboxActive=true>> MailboxURI=imaps://e3.vvm.mstore.msg.t-mobile.com/INBOX>> MailboxAuth=AUTH=PLAIN>> UseMailboxInterface=false>> MailboxStartTLS=false>> MailboxLanguage=1|2|3|4>> GreetingLength=180>> VSLength=10>> TUIPasswordLength=4-9>> MailboxVVMType=cvvm>> MailboxLegacyTLS=false>>>>Yes I already found the VVM config file located at>~/.vvm/modemmanager/vvm. Mine also looks very similar to yours (I am on>MetroPCS which is also owned by T-Mobile in US):>>[Modem Manager]>VVMEnabled=true>VVMType=cvvm>VVMDestinationNumber=127>CarrierPrefix=//VVM>DefaultModemNumber=NULL>ProvisionStatus=2>IMSI=XXXXXXXXXXXXXXX>>[Settings]>MailboxHostname=vvm.mstore.msg.t-mobile.com>MailboxPort=148>MailboxUsername=XXXXXXXXXXX>MailboxPassword=XXXXXXXXXXX>MailboxActive=true>MailboxURI=imaps://vvm.mstore.msg.t-mobile.com/INBOX>MailboxAuth=AUTH=PLAIN>UseMailboxInterface=false>MailboxStartTLS=false>MailboxLanguage=1|2|3|4>GreetingLength=180>VSLength=10>TUIPasswordLength=4-9>MailboxVVMType=cvvm>>Near as I can tell (from looking at messages I receive from '127') this>seems to be the correct info(?).>>> A lot of that was auto-populated already so I only had to change a few>> things.>>Like you, mine was already auto-populated (IIRC).>>But I'm very curious what changes you might have made? :)>>> Once that is done, vvm messages will come in as regular messages as far>> as sxmo is concerned.>>>> vvmd has good debug log and kopi is pretty prompt about helping debug,>> but you can also send the debug here and I can look at it (or in irc)>>Which debug log are we talking about? I see>~/.local/share/sxmo/modem/modemlog.tsv, is there another one specific to>vvm? I looked in /var/log and checked vvm docs, but not finding it yet.>>Cheers,>TRS-80
Ok, I think you probably do need mmsd working, or probably the dns part
of that, but I guess we'll see. The log would be vvms log --- set
SXMO_VVMD_ARGS to -d and then monitor ~/.local/state/*/vvmd*.log or
whatever. (Or just launch vvmd -d)
See what it barks at you.
--
sic dicit magister P
https://phartman.sites.luc.edu/
GPG keyID 0xE0DBD3D6 (CAE6 3A6F 755F 7BC3 36CA 330D B3E6 39C6 E0DB D3D6)
"Hartman, Peter" <phartman@luc.edu> writes:
> Ok, I think you probably do need mmsd working, or probably the dns part > of that, but I guess we'll see.
Yes, I remember reading about the DNS part and trying to get that to
work as well, but not sure I was doing it correctly.
> The log would be vvms log --- set SXMO_VVMD_ARGS to -d and then> monitor ~/.local/state/*/vvmd*.log or whatever. (Or just launch vvmd> -d)
I apologize, but I am a Debian guy, and so I got used to SystemD
commands for starting and stopping services. The following is still
very unclear to me (even after reading docs):
What is difference between sxmo_daemons.sh and the 'normal' way to start
and stop daemons in Alpine/SXMO (rc-service)?
Because I think that vvmd may already be running(?). Anyway, doing
`vvmd -d` exits with error (maybe because already running?):
pine64-pinephone:~$ rc-service vvmd
* rc-service: service `vvmd' does not exist
pine64-pinephone:~$ rc-service vvmd stop
* rc-service: service `vvmd' does not exist
pine64-pinephone:~$ vvmd -d
vvmd[28377]: vvmd version 0.8
vvmd[28377]: ../src/main.c:on_bus_acquired() Dbus Bus acquired!
vvmd[28377]: ../src/service.c:__vvm_service_init() Starting Up VVMD Service Manager
vvmd[28377]: ../src/plugin.c:__vvm_plugin_init()
vvmd[28377]: ../plugins/modemmanager.c:modemmanager_init() Starting Modem Manager Plugin!
vvmd[28377]: ../src/service.c:vvm_service_create() service 0xffffbaa49e90
vvmd[28377]: ../src/service.c:vvm_service_set_identity() service 0xffffbaa49e90 identity modemmanager
vvmd[28377]: ../src/plugin.c:add_plugin() Plugin modemmanager loaded
vvmd[28377]: Lost Dbus Connection! Exiting....
pine64-pinephone:~$ rc-status
Runlevel: default
sxmo-setpermissions [ started ]
dbus [ started ]
nftables [ started ]
haveged [ started ]
wpa_supplicant [ started 20:52:07 (0) ]
networkmanager [ started 20:52:07 (0) ]
chronyd [ started ]
udev-postmount [ started ]
sshd [ started ]
modemmanager [ started 20:52:06 (0) ]
gpsd [ started ]
eg25-manager [ started 20:52:06 (0) ]
swapfile [ started ]
gpsd_pinephone [ started ]
hkdm [ started 20:52:06 (0) ]
rfkill [ started ]
seatd [ started ]
tinydm [ started 20:52:05 (0) ]
local [ started ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
sysfs [ started ]
fsck [ started ]
root [ started ]
localmount [ started ]
loopback [ started ]
Dynamic Runlevel: manual
pine64-pinephone:~$ sxmo_daemons.sh running modem_monitor_vvm
modem_monitor_vvm is still running
pine64-pinephone:~$ sxmo_daemons.sh running modem_monitor_mms
modem_monitor_mms is still running
Aren (in IRC) pointed me to the location of the vvmd logs, doing:
grep 'vvmd' .local/state/superd.log
yielded:
2022/11/10 13:21:07 manager [INFO]: --/usr/share/superd/services/vvmd.service
2022/11/10 13:21:09 vvmd [DEBUG]: vvmd[2636]: vvmd version 0.8
2022/11/10 13:21:09 vvmd [DEBUG]: vvmd[2636]: Could not connect to modem
2022/11/10 13:21:17 vvmd [DEBUG]: vvmd[2636]: New Object does not have Messaging feature, ignoring....
2022/11/10 13:21:19 vvmd [DEBUG]: vvmd[2636]: Modem is not ready to process any unsent/unreceived VVM messages.
2022/11/10 13:21:19 vvmd [DEBUG]: vvmd[2636]: Modem is not ready to process any unsent/unreceived VVM messages.
2022/11/10 13:21:19 vvmd [DEBUG]: vvmd[2636]: Modem is not ready to process any unsent/unreceived VVM messages.
2022/11/10 13:21:43 vvmd [DEBUG]: vvmd[2636]: Unable to activate mailbox!
2022/11/10 13:21:43 vvmd [DEBUG]: vvmd[2636]: You may not get any SMS SYNC Messages until the mailbox is active.
(...which basically kept repeating...)
He also pointed me to https://gitlab.com/kop316/vvmd/-/issues/12, not
sure if that's related or not yet.
Cheers,
TRS-80
On Fri, Nov 11, 2022 at 10:48:08AM -0500, TRS-80 wrote:
>"Hartman, Peter" <phartman@luc.edu> writes:>>> Ok, I think you probably do need mmsd working, or probably the dns part>> of that, but I guess we'll see.>>Yes, I remember reading about the DNS part and trying to get that to>work as well, but not sure I was doing it correctly.
Try:
ping -I wwan0 whateverurlisinthefile
That'll tell you at least if the dns is right.
>>> The log would be vvms log --- set SXMO_VVMD_ARGS to -d and then>> monitor ~/.local/state/*/vvmd*.log or whatever. (Or just launch vvmd>> -d)>>I apologize, but I am a Debian guy, and so I got used to SystemD>commands for starting and stopping services. The following is still>very unclear to me (even after reading docs):
We use superd to stat/stop vvmd. See sxmo_hook_start.sh.
So just:
superctl stop vvmd
and then run vvmd -d by hand
>>2022/11/10 13:21:07 manager [INFO]: --/usr/share/superd/services/vvmd.service>2022/11/10 13:21:09 vvmd [DEBUG]: vvmd[2636]: vvmd version 0.8>2022/11/10 13:21:09 vvmd [DEBUG]: vvmd[2636]: Could not connect to modem>2022/11/10 13:21:17 vvmd [DEBUG]: vvmd[2636]: New Object does not have Messaging feature, ignoring....>2022/11/10 13:21:19 vvmd [DEBUG]: vvmd[2636]: Modem is not ready to process any unsent/unreceived VVM messages.>2022/11/10 13:21:19 vvmd [DEBUG]: vvmd[2636]: Modem is not ready to process any unsent/unreceived VVM messages.>2022/11/10 13:21:19 vvmd [DEBUG]: vvmd[2636]: Modem is not ready to process any unsent/unreceived VVM messages.>2022/11/10 13:21:43 vvmd [DEBUG]: vvmd[2636]: Unable to activate mailbox!>2022/11/10 13:21:43 vvmd [DEBUG]: vvmd[2636]: You may not get any SMS SYNC Messages until the mailbox is active.>>(...which basically kept repeating...)>>He also pointed me to https://gitlab.com/kop316/vvmd/-/issues/12, not>sure if that's related or not yet.
Ok, it looks like it is doing stuff and maybe its vvm's problem not
sxmo... not sure. What does -d show?
--
sic dicit magister P
https://phartman.sites.luc.edu/
GPG keyID 0xE0DBD3D6 (CAE6 3A6F 755F 7BC3 36CA 330D B3E6 39C6 E0DB D3D6)
In IRC, wart_ had the idea to try and check DNS in the mobile network,
so I did:
pine64-pinephone:~$ ping -I wwan0 vvm.mstore.msg.t-mobile.com
PING vvm.mstore.msg.t-mobile.com (2607:fb90:c13e:fff3::2): 56 data bytes
64 bytes from 2607:fb90:c13e:fff3::2: seq=0 ttl=55 time=773.702 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=2 ttl=55 time=476.503 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=3 ttl=55 time=222.383 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=6 ttl=55 time=175.082 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=7 ttl=55 time=204.936 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=8 ttl=55 time=356.556 ms
^C
--- vvm.mstore.msg.t-mobile.com ping statistics ---
10 packets transmitted, 6 packets received, 40% packet loss
round-trip min/avg/max = 175.082/368.193/773.702 ms
pine64-pinephone:~$ ping -I wwan0 vvm.mstore.msg.t-mobile.com
PING vvm.mstore.msg.t-mobile.com (2607:fb90:c13e:fff3::2): 56 data bytes
64 bytes from 2607:fb90:c13e:fff3::2: seq=0 ttl=55 time=237.529 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=1 ttl=55 time=653.105 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=2 ttl=55 time=292.147 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=3 ttl=55 time=563.443 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=6 ttl=55 time=255.524 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=7 ttl=55 time=129.367 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=8 ttl=55 time=169.902 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=9 ttl=55 time=178.684 ms
64 bytes from 2607:fb90:c13e:fff3::2: seq=10 ttl=55 time=164.345 ms
^C
--- vvm.mstore.msg.t-mobile.com ping statistics ---
11 packets transmitted, 9 packets received, 18% packet loss
round-trip min/avg/max = 129.367/293.782/653.105 ms
So, I guess it's not that.
One more data point, this did 'just work' in Mobian, when I was using
that. At some point I think I cross referenced the config files, and
they were the same (might need to double check that).
In fact, I think I will go and do so now.
Cheers,
TRS-80
After my last email, and further diagnostics in IRC, I think I am
hitting this bug:
https://gitlab.com/kop316/vvmd/-/issues/12
I sat down this evening to compile curl with the patch, which is the
workaround mentioned in this post:
https://gitlab.com/kop316/vvmd/-/issues/12#note_1059769797
But then I realized all the commands would be different on SXMO, being
PostmarketOS (Alpine) based.
I am a Debian guy, and quite out of my depth here, so any help would be
appreciated.
Cheers,
TRS-80