search

Sunr1ses / google-voice-sipsorcery-dialplans

Automatically exported from code.google.com/p/google-voice-sipsorcery-dialplans
1 stars 0 forks source link

Sipsorcery/Client issue (please help :D) #109

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Dial a number from Nimbuzz, or Xlite (both clients for SIP)

What is the expected output? What do you see instead?
The SIPphone client makes the ringing sound, finally disconnects.

Please provide any additional information below.

DialPlan 21:05:35:244 sip1(7284): New call from udp:194.178.110.156:23747 
successfully authenticated by digest.
DialPlan 21:05:35:275 sip1(7284): Using dialplan default for Out call to 
sip:+1[PHONE NUMBER I AM CALLING]@sipsorcery.com.
NewCall 21:05:35:275 sip1(7284): Executing script dial plan for call to +[PHONE 
NUMBER I AM CALLING].
DialPlan 21:05:35:385 sip1(7284): ** Call from "[SIPSORCERY 
USERNAME]@sipsorcery.com" 
<sip:[SIPSORCEERYUSERNAME]@sipsorcery.com>;tag=[sipsorc.username]sip129054575919
6 to +1[PHONE NUMBER I AM CALLING] **
DialPlan 21:05:35:400 sip1(7284): Local time: 11/23/2010 16:05
DialPlan 21:05:35:416 sip1(7284): Number in ENUM format: 1[PHONE NUMBER I AM 
CALLING]
DialPlan 21:05:35:432 sip1(7284): SDP on GoogleVoiceCall call had public IP not 
mangled, RTP socket 173.50.140.103:61348.
DialPlan 21:05:35:432 sip1(7284): UAS call progressing with Ringing.
DialPlan 21:05:35:432 sip1(7284): Logging into google.com for [GOOGLE VOICE 
ACCOUNT]@gmail.com.
DialPlan 21:05:35:463 sip1(7284): Google Voice pre-login page loaded 
successfully.
DialPlan 21:05:35:463 sip1(7284): GALX key La19T_nZq38 successfully retrieved.
DialPlan 21:05:36:354 sip1(7284): Google Voice home page loaded successfully.
DialPlan 21:05:36:385 sip1(7284): Call key wkSmrT4u848FfDCHEk+nfAtzjC0= 
successfully retrieved for [GVOICE ACCOUNT]@gmail.com, proceeding with callback.
DialPlan 21:05:36:400 sip1(1704): SIP Proxy setting application server for next 
call to user aclarrabee3 as udp:69.59.142.213:5070.
DialPlan 21:05:36:463 sip1(7284): Google Voice Call to 15036904365 forwarding 
to [SIPGATE PHONE NUMBER] successfully initiated, callback timeout=30s.
DialPlan 21:06:06:462 sip1(7284): Google Voice Call timed out waiting for 
callback.
DialPlan 21:06:06:915 sip1(7284): Google Voice Call to 1[PHONE NUMBER I AM 
CALLING] was successfully cancelled.
DialPlan 21:06:06:915 sip1(7284): GoogleVoiceCall failed, routing thru SIPGate
DialPlan 21:06:06:931 sip1(7284): Destination - North America non-GV
DialPlan 21:06:06:931 sip1(7284): Commencing Dial with: 
*********************************I think this "041" thing might be the issue, I 
could be wrong, but I don't know what it means or how to change it 
*************************
041[PHONE NUMBER I AM CALLING]@Sipgate.
DialPlan 21:06:06:931 sip1(7284): Attempting to locate a provider for call leg: 
sip:041[PHONE NUMBER I AM CALLING]@Sipgate.
DialPlan 21:06:06:931 sip1(7284): ForkCall commencing call leg to 
sip:0415036904365@sipgate.com.
DialPlan 21:06:06:931 sip1(7284): SIPClientUserAgent Call using alternate 
outbound proxy of udp:69.59.142.213:5060.
DialPlan 21:06:06:931 sip1(7284): Switching to sip:041[PHONE NUMBER I AM 
CALLING]@sipgate.com:5060 via udp:69.59.142.213:5060.
DialPlan 21:06:06:931 sip1(7284): SDP on UAC call had public IP not mangled, 
RTP socket 173.50.140.103:61348.

************ERROR I always get is (illegal format*************

DialPlan 21:06:07:056 sip1(7284): Response 404 Not found (illegal format) for 
sip:041[PHONE NUMBER I AM CALLING]@sipgate.com.
DialPlan 21:06:07:056 sip1(7284): Call failed: code 404, Not found (illegal 
format)
DialPlan 21:06:07:056 sip1(7284): UAS call failed with a response status of 404 
and Not found (illegal format).
DialPlan 21:06:07:056 sip1(7284): Dialplan cleanup for aclarrabee3.
DialPlan 21:06:07:306 sip1(7284): Dial plan execution completed with normal 
clearing.

Original issue reported on code.google.com by aligzand...@gmail.com on 23 Nov 2010 at 9:15

GoogleCodeExporter commented 9 years ago 
Now I get this.
I did read that the SIPGATE calling from clients isn't working, is that the 
problem...?

Monitor 04:57:23:404: basetype=console, ipaddress=*, user=aclarrabee3, event=*, 
request=*, serveripaddress=*, server=*, regex=.*.
DialPlan 04:57:39:185 sip1(5440): New call from udp:173.50.140.103:35124 
successfully authenticated by digest.
DialPlan 04:57:39:231 sip1(5440): Using dialplan default for Out call to 
sip:5036904365@sipsorcery.com.
NewCall 04:57:39:247 sip1(5440): Executing script dial plan for call to 
xxxyyyzzzz.
DialPlan 04:57:39:341 sip1(5440): ** Call from "SIPsorcery" 
<sip:USERNAME@sipsorcery.com>;tag=38739479 to xxxyyyzzzz **
DialPlan 04:57:39:341 sip1(5440): Local time: 11/23/2010 23:57
DialPlan 04:57:39:356 sip1(5440): Number in ENUM format: 1xxxyyyzzzz
DialPlan 04:57:39:372 sip1(5440): SDP on GoogleVoiceCall call had RTP socket 
mangled from 192.168.1.2:43348 to 173.50.140.103:43348.
DialPlan 04:57:39:372 sip1(5440): UAS call progressing with Ringing.
DialPlan 04:57:39:372 sip1(5440): Logging into google.com for 
GMAILEMAIL@gmail.com.
DialPlan 04:57:39:419 sip1(5440): Google Voice pre-login page loaded 
successfully.
DialPlan 04:57:39:435 sip1(5440): GALX key 4AxqBDndLrg successfully retrieved.
DialPlan 04:57:41:044 sip1(5440): Google Voice home page loaded successfully.
DialPlan 04:57:41:075 sip1(5440): Call key wkSmrT4u848FfDCHEk+nfAtzjC0= 
successfully retrieved for GMAILEMAIL@gmail.com, proceeding with callback.
DialPlan 04:57:41:091 sip1(1704): SIP Proxy setting application server for next 
call to user USERNAME as udp:69.59.142.213:5070.
DialPlan 04:57:41:169 sip1(5440): Google Voice Call to 1xxxyyyzzzz forwarding 
to SIPGATENUMBER successfully initiated, callback timeout=30s.
DialPlan 04:58:11:169 sip1(5440): Google Voice Call timed out waiting for 
callback.
DialPlan 04:58:11:309 sip1(5440): Google Voice Call to 1xxxyyyzzzz was 
successfully cancelled.
DialPlan 04:58:11:309 sip1(5440): GoogleVoiceCall failed, routing thru SIPGate
DialPlan 04:58:11:387 sip1(5440): Destination - North America non-GV
DialPlan 04:58:11:387 sip1(5440): Commencing Dial with: 041xxxyyyzzzz@Sipgate.
DialPlan 04:58:11:387 sip1(5440): Attempting to locate a provider for call leg: 
sip:041xxxyyyzzzz@Sipgate.
DialPlan 04:58:11:387 sip1(5440): ForkCall commencing call leg to 
sip:0415036904365@sipgate.com.
DialPlan 04:58:11:387 sip1(5440): SIPClientUserAgent Call using alternate 
outbound proxy of udp:69.59.142.213:5060.
DialPlan 04:58:11:387 sip1(5440): Switching to 
sip:041xxxyyyzzzz@sipgate.com:5060 via udp:69.59.142.213:5060.
DialPlan 04:58:11:387 sip1(5440): SDP on UAC call had RTP socket mangled from 
192.168.1.2:43348 to 173.50.140.103:43348.
DialPlan 04:58:11:419 sip1(5440): Response 404 Not found (illegal format) for 
sip:041xxxyyyzzzz@sipgate.com.
DialPlan 04:58:11:434 sip1(5440): Call failed: code 404, Not found (illegal 
format)
DialPlan 04:58:11:434 sip1(5440): UAS call failed with a response status of 404 
and Not found (illegal format).
DialPlan 04:58:11:434 sip1(5440): Dialplan cleanup for USERNAME.
DialPlan 04:58:11:778 sip1(5440): Dial plan execution completed with normal 
clearing.

I also have tried using IPkall, but I don't really like it, I like knowing what 
number is calling me, not just some Washington number, I like the callerID, is 
there any other way of doing this/sipgate working again?

Original comment by aligzand...@gmail.com on 24 Nov 2010 at 5:03

GoogleCodeExporter commented 9 years ago 
Seems like you're using an old complex dialplan and you didn't change the 
selectVSP() method as appropriate. May I suggest that you switch to this 
dialplan:

http://code.google.com/p/google-voice-sipsorcery-dialplans/source/browse/trunk/S
IP+Sorcery+Dial+Plans/Contrib/Simple+Dial+Plan+with+CNAM+and+VM/

Make sure that Sipsorcery registers to your Sipgate account and receives 
incoming call when you call your Sipgate number.

Original comment by mte...@gmail.com on 24 Nov 2010 at 9:45

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
(deleted previous post, I didnt xyz my number out)
Thanks, I tried that.

Is the CB_NUMBER = '1XXXYYYZZZZ'          # my 11-digit GV callback number
GV callback number, in this case, my SipGate number? Or my Google voice number?
I tried it with both, but no luck. 
---
I'm kind of an idiot, I realized that somehow my SipGate number got unlinked 
from my Google Voice number, so now I tried to reactivate, and every time try 
and press the activation numbers on a sip client, NOTHING happens. 
"I'm sorry, I didn't catch that, try again"
I used X-Lite, Nimbuzz, and even the SIPGATE phone.

Thanks for helping me out.

Original comment by aligzand...@gmail.com on 24 Nov 2010 at 11:42

GoogleCodeExporter commented 9 years ago 
> Is the CB_NUMBER = '1XXXYYYZZZZ'          # my 11-digit GV callback number
> GV callback number, in this case, my SipGate number? Or my Google voice 
number?
> I tried it with both, but no luck. 

CB_NUMBER is your Sipgate number (it also can be IPKall, Gizmo or IPCOMMS... 
whatever DID you use for callback and "link" to your GV number).

Of course, if the number is not "linked" (appears on your GV / Voice settings / 
Phones as "Forwards to:"), you're not going to receive callback and the whole 
thing won't work.

> I tried to reactivate, and every time try and press the activation numbers on
> a sip client, NOTHING happens. 
> "I'm sorry, I didn't catch that, try again"
> I used X-Lite, Nimbuzz, and even the SIPGATE phone.

You should play with software settings rather than switch from one SIP client 
to the other (they all might be configured to use the same method for sending 
DTMF).

There are 3 different methods of DTMF transmission, and you need to know which 
to use or to try all methods:

* In-band DTMF
* RTP telephone-event per RFC 2833
* SIP INFO per RFC 2976

Most likely the first method (in-band DTMF) will help. You may also need to 
play with DTMF tone duration (try something within 50..100 ms range).

Original comment by mte...@gmail.com on 25 Nov 2010 at 5:25

GoogleCodeExporter commented 9 years ago 
Thanks for the help. It's all working now.

Original comment by aligzand...@gmail.com on 26 Nov 2010 at 7:49

GoogleCodeExporter commented 9 years ago 
You're welcome! :)

Original comment by mte...@gmail.com on 26 Nov 2010 at 9:48