| reply to Teksavvy1
Re: DLink VTA-VR Howdy folks. I know this thread is kinda outta control and prolly not too many of you are still keeping up with it but I have a question about this little device.
After scratching my head for a couple hours and making a x-over cable so that I could view what was going on with my VTA via wireshark I discovered that most alpha characters in the "caller id number" entry will not properly get passed. Any characters other than A,B,C or D will get passed as an asterisk(*). This is a major problem since some providers use alpha characters in the username. I've tried various firmwares to no avail. My next step is to try and load the PAP2v2 firmware on my VTA, something I would rather not do since the VTA 1.08-NA2 firmware seems to do everything I need - EXCEPT passing alpha characters.
Has anyone found a way to get around this problem?
On another note, I've seen several references to people porting asterisk to this little box which would ROCK, but I haven't seen anyone who has made this work perfectly yet. If anyone has any more info that hasn't already been posted here about running asterisk on the VTA I would love to hear it. Thanks in advance! |
|
cgigate
join:2003-05-12
Fort Worth, TX | reply to mazilo
Re: [General] DLink VTA-VR I have problem with VTA-VR,, many IVR could not recognize the DTMF tone from VTA-VR,
I did not see anywhere can do change RFC2833 parameters. |
|
|
|
 AndrewZPremium
join:2003-07-17
somewhere
2 edits | The only place in the provisioning file related to DTMF:
<DIGIT_RELAY_MODE>1</DIGIT_RELAY_MODE>
Values from dbgcmd:
0 = Relay Disable
1 = Inband DTMF No Report to Host
2 = Inband DTMF Report to Host
3 = Outband DTMF Pass Tones as Voice
4 = Outband DTMF DO NOT Pass Tones as Voice
5 = Move all Tone Detections to Network side
Probably the same may be changed through the dbgcmd directly.
I also have to admit that all (?) CYT devices have problems with DTMF. Some time ago the workaround for this was done on Asterisk. I posted a note on this, try to search. |
|
| Re: [General] DLink VTA-VR - Star codes and dialing plan What is the correct digit map to pass everything to the provider instead of being recognized as a feature (star) code on the phone?
I want everything that I dial, including all starting with a *, to be passed to the provider instead of being recognized by the phone as a feature code.
Could it be somewhere else to change this instead of the digit map to disable all phone * features?
Thanks,
The Doc. |
|
AndrewZPremium
join:2003-07-17
somewhere | Make sure you have the codes defined in your dialplan.
This is the default one:
<DIGIT_MAP>*xxT|*1xx|[349]11|1xxx[2-9]xxxxxx|[2-9]xxxxxxT|[2-9]xxxxxxxxx|011x.T</DIGIT_MAP>
Depending on what you need '*xxT' should be changed to '*xx.T'
You will probably have to disable conflicting feature codes:
<FCODE_CFU></FCODE_CFU>
<FCODE_CFB></FCODE_CFB>
<FCODE_CFN></FCODE_CFN>
<FCODE_CFREACT></FCODE_CFREACT>
<FCODE_CCFWD></FCODE_CCFWD>
<FCODE_CID_BLOCK>*67</FCODE_CID_BLOCK>
<FCODE_CID_UNBLOCK></FCODE_CID_UNBLOCK>
<FCODE_CW_DISABLE></FCODE_CW_DISABLE>
<FCODE_XFER>#90</FCODE_XFER>
<FCODE_AXFER>#91</FCODE_AXFER>
<FCODE_ANON_BLOCK></FCODE_ANON_BLOCK>
<FCODE_ANON_UNBLOCK></FCODE_ANON_UNBLOCK>
<FCODE_DND></FCODE_DND>
<FCODE_RPT_DIAL>#5</FCODE_RPT_DIAL>
<FCODE_CALL_RETURN>*69</FCODE_CALL_RETURN>
<FCODE_EMERGENCY>911</FCODE_EMERGENCY>
<FCODE_PCM_OVERRIDE>*99</FCODE_PCM_OVERRIDE>
|
|
spacez
join:2006-09-30
San Jose, CA | reply to AndrewZ
Re: [General] DLink VTA-VR Thanks AndresZ! I set my digital relay mode to 2 and I can accept calls forwarded from grandcentral through my gizmoproject now. |
|
| reply to mazilo
Hi,
I recently acquired a used VTA which had been provisioned. I have tried to unlock with cyt36, cyt39c, cyt46 without success. After reading this thread again I noticed that the firmware version of my VTA 11.4.0-r060331-1.00.08-r061127.img
Reading posts a few pages back it appears that other people with the 1.00.08 firmware have had similar difficulties in unlocking it.
So what are my options?
1) Should I put the VTA on the internet and hope that it picks up a 1.00.09 firmware which I could downgrade and the do the unlock (as long at Vonage have not patched that bug)
2) Use some other method? I have read the thread and I can't find anyone who has succeeded with the 1.00.08 firmware.
3) Make a serial console. Never done this before in my life!
What should I do??? |
|
| reply to mazilo
Any one success connect to the serial console port?
I just can't get anything on my putty window...
I was followed this »sodoityourself.com/max232-serial···nverter/ |
|
| never mind... RX and TX is reverse...
:P
Works good.
Thanks |
|
cgigate
join:2003-05-12
Fort Worth, TX
1 edit | reply to zaheer2003
said by zaheer2003 :
Hi,
I recently acquired a used VTA which had been provisioned. I have tried to unlock with cyt36, cyt39c, cyt46 without success. After reading this thread again I noticed that the firmware version of my VTA 11.4.0-r060331-1.00.08-r061127.img
Reading posts a few pages back it appears that other people with the 1.00.08 firmware have had similar difficulties in unlocking it.
So what are my options?
1.00.08 is easy to unlock, just like 1-2-3!
if you cannot unlock it, send some $$ to get it unlocked! |
|
| I managed to unlock it after a bit of trial and error, without the $$! I downgraded to 1.07, then Cyt'ed, got the encryption key, then fed it my own XML with TFTP, then upgraded to 1.08NA2.
The problem I am having now is getting 1.08NA2 formware to stick. As advised by rclink I did a factory reset after upgrading to 1.08NA2, clearing provisioned and non provisioned parameters, upon which it goes back to 1.07 unlocked D-Link Firmware (can still access support). Then I have to do the whole CYT thing again.
I have tried just doing the factory reset of the provisioned parameters alonme and it does the same thing! These D-Links are POS, not a patch on PAP2! Also having to press # at the end of the number is annoying me too. Anyway to get rid of it? |
|
| Please could you give me a step be step guide on how you downgrade the frimware as I'm having some problems I have managed to get to the provision server screen then is just stays there. I have f/w 1.00.07 0n the back of the box but 1.0.8 in the firmware page.
thanks in advance for your help
Stew |
|
| hi
I've unlocked a vta and got it dialing out with voipstunt and ringing in on line 2 with sipgate however i cannot dialout with sipgate i think its the dialplan which is wrong but i can't change it easily since i cant get cyt to recognise | when i enter it i think *xx|xx is whats needed but without | i am stuck |
|
| why don't you use the xml file to change the digit map and feed it to your vta??? Sounds a lot easier than using CYT |
|
| reply to mazilo
oh,I'm back on this post again. This time I got trouble. When I was trying to modify my Gizmo digitmap yesterday, my VTA automatically upgrade to 1.0.9 version. Then I downgraded firmware to 1.0.7 and also blocked any ip address about vonage.net in my router. I guess it can't upgrade by itself anymore. Then I tftp the xml to VTA. The problem is coming.
The power led is always blinking. I sshed to VTA and pull the provision.xml file and found it's empty. Also the VOIP section in webpage doesn't reflect my configuration. It seems my xml isn't accepted by VTA. But tftp did transport xml file to VTA. As I know, it could be due to the xml file format. It must be UNIX terminator format. I check the xml file with Ultraedit. It doesn't include 0D. only 0A. In case it's not correct, I save xml file again by choosing UNIX terminator. But my VTA power led is still blinking.
I can't figure it out now. Totally no clue la. Is there any reason why the power led is blinking? Is my box bricked?
Thank you guys.
Sigh....
Lou |
|
| Hi there,
Just following this post and flash my VTA with modded 1.0.8NA firmware. I can set up the phone line in webpage now. The factory settings are also modified with my own setting. Only weird thing is I can't modify the DigitMap in webpage, it won't save. I can SSH the VTA and set tcid digitmap. Commit and activate. But it will be lost after I reboot the VTA. Through the post, I didn't find how to solve this issue. If no solution. I think I just wait for my serial console cable and flash my box completely.
Thank you. Have a good weekend.
Lou |
|
| Please can you let me know where I can get hold of the modded 1.08na firmware
Cheers
Stew |
|
| check this post
»Re: vta 1.00.08 firmware |
|
| reply to mazilo
I try to find the connector for VTA to do the firemware flash. The connector should be like the picture. I searched for a while and didn't find it. Please help. Thank you. |
|
