islandtech
Wassamassaw
- Joined
- Jan 11, 2009
- Messages
- 677
- Reaction score
- 137
Should you be able to call the DID that Vitelity assigned to the Vitelity FMC phone? I get a line busy when calling it from any phone.
[2014-07-08 14:26:53] VERBOSE[9934] chan_sip.c:
ÿ<--- SIP read from UDP:66.241.99.181:5060 --->
ÿINVITE sip:[email protected]:5060 SIP/2.0
ÿVia: SIP/2.0/UDP 66.241.99.181:5060;branch=z9hG4bK5c936bf9;rport
ÿFrom: "+1843902xxx" <sip:[email protected]>;tag=as56ad7b18
ÿTo: <sip:[email protected]:5060>
ÿContact: <sip:[email protected]>
ÿCall-ID: [email protected]
ÿCSeq: 102 INVITE
ÿUser-Agent: packetrino
ÿMax-Forwards: 70
ÿDate: Tue, 08 Jul 2014 18:26:52 GMT
ÿAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
ÿSupported: replaces
ÿContent-Type: application/sdp
ÿContent-Length: 332
ÿ
ÿv=0
ÿo=root 810 810 IN IP4 66.241.99.181
ÿs=session
ÿc=IN IP4 66.241.99.181
ÿt=0 0
ÿm=audio 15764 RTP/AVP 0 8 3 18 101
ÿa=rtpmap:0 PCMU/8000
ÿa=rtpmap:8 PCMA/8000
ÿa=rtpmap:3 GSM/8000
ÿa=rtpmap:18 G729/8000
ÿa=fmtp:18 annexb=no
ÿa=rtpmap:101 telephone-event/8000
ÿa=fmtp:101 0-16
ÿa=silenceSupp:off - - - -
ÿa=ptime:20
ÿa=sendrecv
ÿ<------------->
[2014-07-08 14:26:53] VERBOSE[9934] chan_sip.c: --- (14 headers 16 lines) ---
[2014-07-08 14:26:53] VERBOSE[9934] chan_sip.c: Sending to 66.241.99.181:5060 (NAT)
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c: Sending to 66.241.99.181:5060 (NAT)
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c: Using INVITE request as basis request - [email protected]
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c: No matching peer for '843902xxx' from '66.241.99.181:5060'
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c:
ÿ<--- Reliably Transmitting (NAT) to 66.241.99.181:5060 --->
ÿSIP/2.0 401 Unauthorized
ÿVia: SIP/2.0/UDP 66.241.99.181:5060;branch=z9hG4bK5c936bf9;received=66.241.99.181;rport=5060
ÿFrom: "+1843902xxx" <sip:[email protected]>;tag=as56ad7b18
ÿTo: <sip:[email protected]:5060>;tag=as3a1a3e50
ÿCall-ID: [email protected]
ÿCSeq: 102 INVITE
ÿServer: FPBX-2.11.0(11.10.0)
ÿAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
ÿSupported: replaces, timer
ÿWWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="00540288"
ÿContent-Length: 0
ÿ
ÿ
ÿ<------------>
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: INVITE)
[2014-07-08 14:26:53] VERBOSE[9934] chan_sip.c:
ÿ<--- SIP read from UDP:66.241.99.181:5060 --->
ÿACK sip:[email protected]:5060 SIP/2.0
ÿVia: SIP/2.0/UDP 66.241.99.181:5060;branch=z9hG4bK5c936bf9;rport
ÿFrom: "+1843902xxx" <sip:[email protected]>;tag=as56ad7b18
ÿTo: <sip:[email protected]:5060>;tag=as3a1a3e50
ÿContact: <sip:[email protected]>
ÿCall-ID: [email protected]
ÿCSeq: 102 ACK
ÿUser-Agent: packetrino
ÿMax-Forwards: 70
ÿContent-Length: 0
ÿ
ÿ<------------->
[2014-07-08 14:26:53] VERBOSE[9934] chan_sip.c: --- (10 headers 0 lines) ---
[2014-07-08 14:26:53] VERBOSE[9934] chan_sip.c:
ÿ<--- SIP read from UDP:66.241.99.181:5060 --->
ÿINVITE sip:[email protected]:5060 SIP/2.0
ÿVia: SIP/2.0/UDP 66.241.99.181:5060;branch=z9hG4bK2384a435;rport
ÿFrom: "+1843902xxx" <sip:[email protected]>;tag=as56ad7b18
ÿTo: <sip:[email protected]:5060>
ÿContact: <sip:[email protected]>
ÿCall-ID: [email protected]
ÿCSeq: 103 INVITE
ÿUser-Agent: packetrino
ÿMax-Forwards: 70
ÿAuthorization: Digest username="name_24.211.ccc.ddd", realm="asterisk", algorithm=MD5, uri="sip:[email protected]:5060", nonce="00540288", response="fefdbae878a6f114e43e0772560e59e9"
ÿDate: Tue, 08 Jul 2014 18:26:52 GMT
ÿAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
ÿSupported: replaces
ÿContent-Type: application/sdp
ÿContent-Length: 332
ÿ
ÿv=0
ÿo=root 810 811 IN IP4 66.241.99.181
ÿs=session
ÿc=IN IP4 66.241.99.181
ÿt=0 0
ÿm=audio 15764 RTP/AVP 0 8 3 18 101
ÿa=rtpmap:0 PCMU/8000
ÿa=rtpmap:8 PCMA/8000
ÿa=rtpmap:3 GSM/8000
ÿa=rtpmap:18 G729/8000
ÿa=fmtp:18 annexb=no
ÿa=rtpmap:101 telephone-event/8000
ÿa=fmtp:101 0-16
ÿa=silenceSupp:off - - - -
ÿa=ptime:20
ÿa=sendrecv
ÿ<------------->
[2014-07-08 14:26:53] VERBOSE[9934] chan_sip.c: --- (15 headers 16 lines) ---
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c: Sending to 66.241.99.181:5060 (NAT)
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c: Using INVITE request as basis request - [email protected]
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c: No matching peer for '843902xxx' from '66.241.99.181:5060'
[2014-07-08 14:26:53] NOTICE[9934][C-00000033] chan_sip.c: Failed to authenticate device "+1843902xxx" <sip:[email protected]>;tag=as56ad7b18
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c:
ÿ<--- Reliably Transmitting (NAT) to 66.241.99.181:5060 --->
ÿSIP/2.0 403 Forbidden
ÿVia: SIP/2.0/UDP 66.241.99.181:5060;branch=z9hG4bK2384a435;received=66.241.99.181;rport=5060
ÿFrom: "+1843902xxx" <sip:[email protected]>;tag=as56ad7b18
ÿTo: <sip:[email protected]:5060>;tag=as3a1a3e50
ÿCall-ID: [email protected]
ÿCSeq: 103 INVITE
ÿServer: FPBX-2.11.0(11.10.0)
ÿAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
ÿSupported: replaces, timer
ÿContent-Length: 0
ÿ
ÿ
ÿ<------------>
[2014-07-08 14:26:53] VERBOSE[9934][C-00000033] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: INVITE)
[2014-07-08 14:26:53] VERBOSE[9934] chan_sip.c:
ÿ<--- SIP read from UDP:66.241.99.181:5060 --->
ÿACK sip:[email protected]:5060 SIP/2.0
ÿVia: SIP/2.0/UDP 66.241.99.181:5060;branch=z9hG4bK2384a435;rport
ÿFrom: "+1843902xxx" <sip:[email protected]>;tag=as56ad7b18
ÿTo: <sip:[email protected]:5060>;tag=as3a1a3e50
ÿContact: <sip:[email protected]>
ÿCall-ID: [email protected]
ÿCSeq: 103 ACK
ÿUser-Agent: packetrino
ÿMax-Forwards: 70
ÿContent-Length: 0
ÿ
ÿ<------------->
VMobile is dead. It never worked well anyway and Vitelity advised me not to buy it in the first place.It looks like "the corporate suck" has set in post-Onvoy acquisition, and the vMobile offering has been put out to pasture.
Option to purchase vMobile devices has disappeared from my portal and a support ticket I opened about the service has remained unanswered for over a month now.
Getting real tired of this phenomenon.
Are you saying they just turned it off?VMobile is dead. It never worked well anyway and Vitelity advised me not to buy it in the first place.
I don't know if it's turned off.Are you saying they just turned it off?
had to install their SMS client just to get the texting working again
I don't know if it's turned off.
At least they aren't selling it anymore and have dropped support for it.
It's S.MS. I had to side load it as it wasn't in the Google Play Store. You can also use about any XMPP chat client to connect to their third party SMS provider.What client is that?
Link up your team and customers Phone System Live Chat Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.