Attempt to dial up is failing on my Verizon EV3 device. What is wrong?

If you have an account through an MVNO like Crossbridge that is using the Verizon network, then it is possible that the account is not yet valid in the Verizon system. By default, the EV3 cellular radio will authenticate with the network using MIP, but attempt SIP if MIP fails (this setting is called MIP Preferred). If the account is not yet valid in Verizon's system, then MIP will fail and the device will try SIP. When using SIP, then the PPP dial-up connection will require CHAP authentication. Since the account is not yet valid, then the PPP dial-up connection will also fail.

Having access to the PPP dial-up connection logs that show the LCP request details will help diagnose this situation. For example, the following are PPP logs from the messages log file in Linux (the Linux ppptrace file does not show LCP request details and is not useful for this type of troubleshooting).

Successful Connection (Note there is no auth chap MD5 request. The EV3 likely connected to the network using MIP before the PPP dial-up attempt.):
2015-07-29T09:19:31-04:00 rcell pppd: rcvd [LCP ConfReq id=0x4 < asyncmap 0x0> < magic 0x49d1f42a> < pcomp> < accomp>]
2015-07-29T09:19:31-04:00 rcell pppd: sent [LCP ConfAck id=0x4 < asyncmap 0x0> < magic 0x49d1f42a> < pcomp> < accomp>]
2015-07-29T09:19:31-04:00 rcell pppd: sent [IPCP ConfReq id=0x3 < addr 0.0.0.0> < ms-dns1 0.0.0.0> < ms-dns3 0.0.0.0>]
2015-07-29T09:19:31-04:00 rcell pppd: rcvd [LCP DiscReq id=0x5 magic=0x49d1f42a]
2015-07-29T09:19:31-04:00 rcell pppd: rcvd [IPCP ConfReq id=0x1 < addr 10.11.12.13>]
2015-07-29T09:19:31-04:00 rcell pppd: sent [IPCP ConfAck id=0x1 < addr 10.11.12.13>]
2015-07-29T09:19:31-04:00 rcell pppd: rcvd [IPCP ConfNak id=0x3 < addr 10.241.242.243> < ms-dns1 10.244.189.10> < ms-dns3 10.244.189.11>]
2015-07-29T09:19:31-04:00 rcell pppd: sent [IPCP ConfReq id=0x4 < addr 10.241.242.243> < ms-dns1 10.244.189.10> < ms-dns3 10.244.189.11>]
2015-07-29T09:19:31-04:00 rcell pppd: rcvd [IPCP ConfAck id=0x4 < addr 10.241.242.243> < ms-dns1 10.244.189.10> < ms-dns3 10.244.189.11>]
2015-07-29T09:19:31-04:00 rcell pppd: Local IP address changed to 10.241.242.243
2015-07-29T09:19:31-04:00 rcell pppd: Remote IP address changed to 10.11.12.13


Failed Connection (Note the auth chap MD5 request. The EV3 likely connected to the network using SIP as a result of MIP failure before the PPP dial-up attempt.):
2015-07-28T09:53:58-04:00 rcell pppd: rcvd [LCP ConfReq id=0x2 < asyncmap 0x0> < auth chap MD5> < magic 0x8ec9b690> < pcomp> < accomp>]
2015-07-28T09:53:58-04:00 rcell pppd: sent [LCP ConfAck id=0x2 < asyncmap 0x0> < auth chap MD5> < magic 0x8ec9b690> < pcomp> < accomp>]
2015-07-28T09:53:58-04:00 rcell pppd: rcvd [CHAP Challenge id=0x1 <2131fd88bd1c676aaabf689236d1c754>, name = ]
2015-07-28T09:53:58-04:00 rcell pppd: sent [CHAP Response id=0x1 <46d26ba45f2bde15555d35bce9a19eac>, name = username]
2015-07-28T09:53:58-04:00 rcell pppd: rcvd [CHAP Failure id=0x1 ]
2015-07-28T09:53:58-04:00 rcell pppd: CHAP authentication failed


SOLUTION: Our recommendation if seeing the above CHAP authentication failure is to contact the MVNO and ask if the activation had completed successfully. Activation through to the Verizon system needs to be successful before connection to the network will succeed.


NOTE: This isn't to say that CHAP authentication will always fail. If the network requires SIP, the end-user account is configured correctly, and the end-user has been informed of (and is using) the username and password for the account, then the connection will likely succeed even though it is requiring CHAP authentication.