|
Title: Google Voice Voicemail retrieval Post by: primerisk on July 08, 2012, 07:34:28 am Hi,
I have an Obi110 setup and working great except for retrieving voicemail. When I call my GV number from the Obi all I ever get is a fast busy signal. If I call from any other number things work as expected. I have tried setting the Google Chat Voicemail Access setting to Yes-PIN Required, Yes-PIN Not Required, and No all with the same results. Does anyone know how to resolve this one? Title: Re: Google Voice Voicemail retrieval Post by: primerisk on July 08, 2012, 08:21:51 am ??? An interesting note, if I go to the Google Voice webpage and use the Call feature to have the Obi call the Google voice number, it throws me right into voicemail (like it should)
Title: Re: Google Voice Voicemail retrieval Post by: jimates on July 08, 2012, 11:40:16 am You are not making an outgoing call from the GV page. It calls you (incoming) and then connects you.
Are you set up on your Obi using your gmail credentials, or are you going through another server, such as simonics GV gateway? Title: Re: Google Voice Voicemail retrieval Post by: primerisk on July 08, 2012, 06:15:12 pm Yes, I'm using my XXXXX@gmail.com credentials directly. I'm not going through any other service.
Title: Re: Google Voice Voicemail retrieval Post by: jimates on July 09, 2012, 08:35:52 am When you call out on your phone connected to the Obi, does your google voice number show as the caller id? If so, no reason it shouldn't work for calling voicemail.
Title: Re: Google Voice Voicemail retrieval Post by: primerisk on July 09, 2012, 05:48:30 pm Yes, the right CID info shows up.
Title: Re: Google Voice Voicemail retrieval Post by: jimates on July 10, 2012, 05:33:50 am Got me stumped. You will have to visit the google help forums and find the form to send google for trouble.
Title: Re: Google Voice Voicemail retrieval Post by: Deltona_Dave on November 04, 2012, 06:56:03 am Wow, since July there has been no resolution to this issue! I have this issue and am also stumped. When I attempt to retrieve GV voicemail by calling my GV number via a phone connected to my Obihai 110 phone port I get a busy signal (GV is my SP1 and GV is setup to retrieve voicemail requiring a pin for access). I tried to diagnose with PhonerLite debug (call my GV number from PhonerLite) but I'm not seeing anything obvious. Below is my debug - anyone have any suggestions? Thanks.
------------------------------------------- 08:14:09,773: T: 127.0.0.1:5060 (UDP) INVITE sip:myGoogleVoicenumber@127.0.0.1 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:62516;branch=z9hG4bK8026aa2fef24e2119601eb78d954abf0;rport From: <sip:mySoftPhonenumber@127.0.0.1>;tag=2883828328 To: <sip:myGoogleVoicenumber@127.0.0.1> Call-ID: 8026AA2F-EF24-E211-9600-EB78D954ABF0@127.0.0.1 CSeq: 2 INVITE Contact: <sip:mySoftPhonenumber@127.0.0.1:62516> Content-Type: application/sdp Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE, UPDATE Max-Forwards: 70 Supported: 100rel, replaces, from-change User-Agent: SIPPER for PhonerLite P-Preferred-Identity: <sip:mySoftPhonenumber@127.0.0.1> Content-Length: 437 v=0 o=- 919299051 1 IN IP4 127.0.0.1 s=SIPPER for PhonerLite c=IN IP4 127.0.0.1 t=0 0 m=audio 62518 RTP/AVP 107 8 0 2 3 97 110 111 9 101 a=rtpmap:107 opus/48000 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=rtpmap:110 speex/8000 a=rtpmap:111 speex/16000 a=rtpmap:9 G722/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ssrc:1739940382 a=sendrecv ------------------------------------------- 08:14:09,774: R: 127.0.0.1:5060 (UDP) SIP/2.0 100 Trying Call-ID: 8026AA2F-EF24-E211-9600-EB78D954ABF0@127.0.0.1 Cseq: 2 INVITE Content-Length: 0 From: <sip:mySoftPhonenumber@127.0.0.1>;tag=2883828328 To: <sip:myGoogleVoicenumber@127.0.0.1>;tag=SP17921375b291c2924 Via: SIP/2.0/UDP 127.0.0.1:62516;branch=z9hG4bK8026aa2fef24e2119601eb78d954abf0;received=127.0.0.1;rport=62516 ------------------------------------------- 08:14:09,777: R: 127.0.0.1:5060 (UDP) SIP/2.0 180 Ringing Call-ID: 8026AA2F-EF24-E211-9600-EB78D954ABF0@127.0.0.1 Cseq: 2 INVITE Content-Length: 0 From: <sip:mySoftPhonenumber@127.0.0.1>;tag=2883828328 To: <sip:myGoogleVoicenumber@127.0.0.1>;tag=SP17921375b291c2924 Via: SIP/2.0/UDP 127.0.0.1:62516;branch=z9hG4bK8026aa2fef24e2119601eb78d954abf0;received=127.0.0.1;rport=62516 08:14:09,778: Info Indication: 0F 00 01 00 08 82 16 00 01 01 00 00 01 80 00 08:14:09,778: Info Indication: alerting 08:14:09,780: Info Response: 0C 00 01 00 08 83 16 00 01 01 00 00 08:14:09,780: Info Response 08:14:09,780: Info Indication: 11 00 01 00 08 82 17 00 01 01 00 00 1E 00 02 81 88 08:14:09,780: Info Indication: in-band information or an appropriate pattern is now available 08:14:09,780: Connect B3 Request: 0D 00 01 00 82 80 D3 0F 01 01 00 00 00 08:14:09,780: Connect B3 Request 08:14:09,780: Info Response: 0C 00 01 00 08 83 17 00 01 01 00 00 08:14:09,780: Info Response 08:14:09,780: Info Indication: 25 00 01 00 08 82 18 00 01 01 00 00 6C 00 16 00 80 34 30 37 35 37 34 38 31 39 30 40 31 32 37 2E 30 2E 30 2E 31 08:14:09,780: Info Indication: myGoogleVoicenumber@127.0.0.1 08:14:09,780: Info Response: 0C 00 01 00 08 83 18 00 01 01 00 00 08:14:09,780: Info Response 08:14:09,783: Connect B3 Confirm: 0E 00 01 00 82 81 D3 0F 01 01 01 00 00 00 08:14:09,783: Connect B3 Confirm 08:14:09,783: Connect B3 Active Indication: 0D 00 01 00 83 82 1A 00 01 01 01 00 00 08:14:09,783: Connect B3 Active Indication 08:14:09,783: Connect B3 Active Response: 0C 00 01 00 83 83 1A 00 01 01 01 00 08:14:09,784: Connect B3 Active Response 08:14:09,784: Facility Request: 19 00 01 00 80 80 D4 0F 01 01 01 00 01 00 0A 01 00 64 00 3C 00 00 00 00 00 08:14:09,784: Facility (DTMF on/off) Request 08:14:09,843: Facility Confirm: 11 00 01 00 80 81 D4 0F 01 00 00 00 00 00 01 00 00 08:14:09,843: Facility Confirm (DTMF) ------------------------------------------- 08:14:11,753: R: 127.0.0.1:5060 (UDP) SIP/2.0 486 Busy Here Call-ID: 8026AA2F-EF24-E211-9600-EB78D954ABF0@127.0.0.1 Cseq: 2 INVITE Content-Length: 0 From: <sip:mySoftPhonenumber@127.0.0.1>;tag=2883828328 To: <sip:myGoogleVoicenumber@127.0.0.1>;tag=SP17921375b291c2924 Via: SIP/2.0/UDP 127.0.0.1:62516;branch=z9hG4bK8026aa2fef24e2119601eb78d954abf0;received=127.0.0.1;rport=62516 ------------------------------------------- 08:14:11,753: T: 127.0.0.1:5060 (UDP) ACK sip:myGoogleVoicenumber@127.0.0.1 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:62516;branch=z9hG4bK8026aa2fef24e2119601eb78d954abf0;rport From: <sip:mySoftPhonenumber@127.0.0.1>;tag=2883828328 To: <sip:myGoogleVoicenumber@127.0.0.1>;tag=SP17921375b291c2924 Call-ID: 8026AA2F-EF24-E211-9600-EB78D954ABF0@127.0.0.1 CSeq: 2 ACK Content-Length: 0 08:14:11,754: Info Indication: 0F 00 01 00 08 82 87 00 01 01 00 00 45 80 00 08:14:11,754: Info Indication: disconnect 08:14:11,754: Info Response: 0C 00 01 00 08 83 87 00 01 01 00 00 08:14:11,754: Info Response 08:14:16,008: Disconnect B3 Indication: 0E 00 01 00 84 82 61 01 01 01 01 00 00 00 08:14:16,008: Disconnect B3 Indication 08:14:16,008: Disconnect B3 Response: 0C 00 01 00 84 83 61 01 01 01 01 00 08:14:16,008: Disconnect B3 Response 08:14:16,008: Disconnect Request: 12 00 01 00 04 80 45 11 01 01 00 00 05 00 00 00 00 00 08:14:16,008: Disconnect Request 08:14:16,015: Disconnect Indication: 0E 00 01 00 04 82 62 01 01 01 00 00 00 34 08:14:16,015: Disconnect Indication: 08:14:16,030: Disconnect Response: 0C 00 01 00 04 83 62 01 01 01 00 00 08:14:16,030: Disconnect Response |