Pin entered for a calling card is not recognized

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Setup GV+Sipsorcery+Sipgate+3cx soft phone to successfully make and receive 
calls.
2.Call a calling card number (for making international calls) which needs a pin 
to be entered after connected. For eg, dial 408-625 4855 and on getting 
connected, dial a 10 digit pin.
3.Before one could complete the dialing of pin, one gets message: invalid pin. 
However one can make these calls(and enter pin) from a mobile successfully.

What is the expected output? What do you see instead?
When the call is connected, the pin entered should be passed as entered, to the 
automated system. But instead, before the 10 digit pin entry is completed, the 
automated system replies that it is invalid pin and asks to enter a correct pin.

What version of the product are you using? On what operating system?
3CX Softphone on Windows Vista.

Please provide any additional information below.
To nail down the issue, I tried using a sipgate softphone registered directly 
to sipgate to receive the call (instead of the 3cx phone registered with 
sipsorcery). The pin I entered was accepted and could proceed without any 
glitches. So, I assume it is a bug in the dial plan. I am using the complex 
dial plan by Mike Telis. Providing you the log from sipsorcery console while 
entering pin, after the call is connected.

....

DialPlan 19:10:41:917 sip1: Google Voice Call callback received.
DialPlan 19:10:41:917 sip1: Answering client call with a response status of 200.
DialPlan 19:10:42:042 sip1: Google Voice Call was successfully answered in 
5.20s.
DialPlan 19:10:42:245 sip1: Dial plan execution completed with normal clearing.
DialPlan 19:10:51:713 sip1: Matching dialogue found for INFO to 
sip:69.59.142.213:5060 from udp:69.59.142.213:5060.
DialPlan 19:10:51:729 sip1: Forwarding in dialogue INFO from 
udp:69.59.142.213:5060 to sip:4084094477@204.155.29.57, first hop 
udp:69.59.142.213:5060.
DialPlan 19:10:51:901 sip1: Forwarding in dialogue response from 
udp:69.59.142.213:5060 INFO final response 200 OK to 69.59.142.213:5060.
DialPlan 19:10:52:198 sip1: Matching dialogue found for INFO to 
sip:69.59.142.213:5060 from udp:69.59.142.213:5060.
DialPlan 19:10:52:245 sip1: Forwarding in dialogue INFO from 
udp:69.59.142.213:5060 to sip:4084094477@204.155.29.57, first hop 
udp:69.59.142.213:5060.
DialPlan 19:10:52:448 sip1: Forwarding in dialogue response from 
udp:69.59.142.213:5060 INFO final response 200 OK to 69.59.142.213:5060.
DialPlan 19:10:52:854 sip1: Matching dialogue found for INFO to 
sip:69.59.142.213:5060 from udp:69.59.142.213:5060.
DialPlan 19:10:52:885 sip1: Forwarding in dialogue INFO from 
udp:69.59.142.213:5060 to sip:4084094477@204.155.29.57, first hop 
udp:69.59.142.213:5060.
DialPlan 19:10:53:026 sip1: Forwarding in dialogue response from 
udp:69.59.142.213:5060 INFO final response 200 OK to 69.59.142.213:5060.
DialPlan 19:10:56:448 sip1: Matching dialogue found for INFO to 
sip:69.59.142.213:5060 from udp:69.59.142.213:5060.
DialPlan 19:10:56:463 sip1: Forwarding in dialogue INFO from 
udp:69.59.142.213:5060 to sip:4084094477@204.155.29.57, first hop 
udp:69.59.142.213:5060.
DialPlan 19:10:56:604 sip1: Forwarding in dialogue response from 
udp:69.59.142.213:5060 INFO final response 200 OK to 69.59.142.213:5060.
DialPlan 19:10:57:213 sip1: Matching dialogue found for INFO to 
sip:69.59.142.213:5060 from udp:69.59.142.213:5060.
DialPlan 19:10:57:229 sip1: Forwarding in dialogue INFO from 
udp:69.59.142.213:5060 to sip:4084094477@204.155.29.57, first hop 
udp:69.59.142.213:5060.
DialPlan 19:10:57:401 sip1: Forwarding in dialogue response from 
udp:69.59.142.213:5060 INFO final response 200 OK to 69.59.142.213:5060.
DialPlan 19:10:57:713 sip1: Matching dialogue found for INFO to 
sip:69.59.142.213:5060 from udp:69.59.142.213:5060.
DialPlan 19:10:57:744 sip1: Forwarding in dialogue INFO from 
udp:69.59.142.213:5060 to sip:4084094477@204.155.29.57, first hop 
udp:69.59.142.213:5060.
DialPlan 19:10:57:823 sip1: Forwarding in dialogue response from 
udp:69.59.142.213:5060 INFO final response 200 OK to 69.59.142.213:5060.
DialPlan 19:10:58:479 sip1: Matching dialogue found for INFO to 
sip:69.59.142.213:5060 from udp:69.59.142.213:5060.
DialPlan 19:10:58:510 sip1: Forwarding in dialogue INFO from 
udp:69.59.142.213:5060 to sip:4084094477@204.155.29.57, first hop 
udp:69.59.142.213:5060.
DialPlan 19:10:58:713 sip1: Forwarding in dialogue response from 
udp:69.59.142.213:5060 INFO final response 200 OK to 69.59.142.213:5060.
DialPlan 19:11:04:260 sip1: Matching dialogue found for BYE to 
sip:69.59.142.213:5060 from udp:69.59.142.213:5060.

Original issue reported on code.google.com by harry.go...@gmail.com on 1 Aug 2010 at 9:57

[GoogleCodeExporter]

Thanks for opening a ticket. It has to do with the way the touch tones are 
passed through to the system. There isn't anything that we could change in the 
dial plan to change the sound quality. You know how while calling out, you hear 
a "local" outbound ring first, and then the sound of the ring changes? The 
second ring you hear is the actual sound of Google Voice connecting your call.

Before you ever hear the second outbound ring the dialplan goes out of the 
picture. The script terminates successfully as soon as the inbound call from 
Google Voice starts ringing on the the SIP Sorcery account. You can see it 
happening at 19:10:42:245 in your output (thank you for that, btw). Have you 
tried other softphones? Have you played with the way touch tones are passed 
over the line? That's where your problem lies.

Original comment by easter...@gmail.com on 2 Aug 2010 at 12:13

• Changed state: Started
• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Thanks for your reply. As per your suggestion, I tried another softphone and it 
worked. So, it must be the problem with 3CX softphone. I had earlier used 
x-lite but uninstalled it after facing an issue where I was not able to hear 
any ring after dialing and the call was not getting connected.

Original comment by harry.go...@gmail.com on 3 Aug 2010 at 3:44

[GoogleCodeExporter]

Glad it worked, Harry. Thanks for coming back to provide an update.

Original comment by easter...@gmail.com on 3 Aug 2010 at 12:54

• Changed state: Invalid