2700 voip functionality

Started by g7pkf, Dec 28, 2007, 20:40:00

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

g7pkf

Okay firstly my appologies for 2 reasons.

i am trying to set up voip on  my 2700 with sbc firmware.

1st apology. I decided it best to start a dedicated thread.

here are the posts from other forums that i have been "playing with". if anyone gets it working please let me know and i will do a proper "How to" and post it on my website.

2nd apology "double posting"

It appears at first glance that upgrading to the 2wire firmware  loses the VOIP functionality but this is not, in fact, the case - it just becomes a little harder to find. Try http://192.168.1.254/?PAGE=V00 (substituting your own router's IP as appropriate, and noting that the last two chars are zeros, not 'oh's).

This PAGE= trick works for other things too, and can access pages which are not otherwise available. I haven't had time to investigate this properly as yet, but have established that pages seem to be grouped by function, with the first alpha (the 'V' in the above url) being the function group, and the following two numerics being the page within the group. So far I have identified the following groups:

A - The router's System pages
B - Broadband link pages
C - Home Network pages
E - Firewall pages
H - Wizards (set-up wizard at H02)
J - 2Wire management console
K - Manual upgrade pages
M - M01 has a Java applet which shows speed graphs for the broadband connection.
V - VOIP pages
Z - There's something here, but I'm getting "not authorised" messages when I try to access them.

I suspect access to the 'Z' pages may be controlled by the key code entered when the router is set up. I'm still using the BT key, so if someone with the 'manual setup' key would like to have a look and report back...?

Similarly, if anyone finds any interesting hidden pages is would be interesting to know.


and the following post

First thing you want to be doing is stopping telstra from updating these things theres two ways to do this firstly using firefox and the webdeveloper toolbar go to home/xslt?PAGE=J30 you will see 2 fields one with remotedsl.bigpond.com and the other with css://...blah blah on the webdev toolbar click on forms->"make form fields writable" you should now be able to modify these two fields. enter anything you like and internal ip address is fine or just a random word just as long as you change whatever was in there before. Make sure "SIP Application Layer Gateway" is enabled and hit submit.
The other way to disable the updating is setting dns entries as mentioned above.

To setup voip click on Disable->disable meta redirects (on the webdev toolbar) and direct your browser to home/xslt?PAGE=J62 click edit next to profile 0 and enter your voip settings, once you have submitted your settings ensure the box next to Profile 0 is checked and hit submit on this page. Now go to home/xslt?PAGE=J65 and "Associate the Line with a Server" set line 1 to whatever you called your voip profile previously, submit. Now go to home/xslt?PAGE=V01 and follow the steps once you get to xslt?PAGE=V03 click edit next to the first phone line make sure username and authname are the same i have network call feature checked but I'm not sure if it makes a difference enter your password for your voip service. submit this info and check the activate box on the first line. you should be right from here just make sure any boxes that say enabled are checked. And there you have it VoIP on your telstra modem. you can check the status on home/xslt?PAGE=V00 to see if it worked or just look at the detailed log (home/mdc down the bottom)

Telstra's attempt at blocking voip configuration involved a meta redirect and a read only field, thats a pretty poor effort from telstra.

btw you should keep meta redirects disabled throughout this procedure otherwise you will be sent to a Page not found error


Im still trying and have nearly had it working-but then broke it and little one came home and.

If anyone cracks it let us know

Dean G7PKF


Rik

No need for apologies, Dean, you should have asked and I would have split the thread off for you. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.