https://support.aa.net.uk/api.php?action=feedcontributions&user=Dagger&feedformat=atomAAISP Support Site - User contributions [en-gb]2024-03-28T10:42:07ZUser contributionsMediaWiki 1.39.5https://support.aa.net.uk/index.php?title=VoIP_-_Transferring_Calls&diff=15245VoIP - Transferring Calls2021-07-26T10:30:30Z<p>Dagger: /* Typical Scenario */ typo</p>
<hr />
<div>__NOTOC__<indicator name="Configuring">[[File:Menu-cog.svg|link=:Category:VoIP Features|30px|Back up to the VoIP Features Category]]</indicator><br />
==Overview==<br />
<br />
Transferring calls to internal or external numbers is supported with most phones. <br />
<br />
See your phone manufacturers' manual for how to do this on your device. Typically, your phone would have a Hold or Transfer button which enables a call to be transferred. <br />
<br />
If you have a SNOM phone, see the '''BELOW''' for help on how to transfer a call.<br />
<br />
<br />
<br />
[[File:SNOM_image_Page_01.jpg|800px]]<br />
<br />
[[File:SNOM_D375_Transferring_Calls.jpg|800px]]<br />
<br />
[[File:SNOM_D375_Transferring_Calls2.jpg|800px]]<br />
<br />
[[File:SNOM D375 Transferring Calls3.jpg|800px]]<br />
<br />
[[File:SNOM D120 Transferring Calls.jpg|800px]]<br />
<br />
[[File:SNOM D120 Transferring Calls2.jpg|800px]]<br />
<br />
[[File:SNOM D120 Transferring Calls3.jpg|800px]]<br />
<br />
[[File:SNOM D712 Transferring Calls.jpg|800px]]<br />
<br />
[[File:SNOM D712 Transferring Calls2.jpg|800px]]<br />
<br />
[[File:SNOM D712 Transferring Calls3.jpg|800px]]<br />
<br />
==Typical Scenario==<br />
With a company having a number staff, we'd suggest that each person, or each handset, has their own phone number. Additional numbers can be setup to be a 'group' or 'main' number which then in turn ring a number of handsets. We can provide numbers in blocks of 10, 20 or more.<br />
<br />
With each phone being on a separate number you can then call or transfer a call to a specific phone. <br />
<br />
To transfer, you can use the full phone number, or you can use the 'Centrex setting on the Control Pages to allow the use of the last 1, 2 or 3 digits of your phone number to call other numbers in your block. e.g. if you have 2 numbers 01344400001 and 01344400002, then you can call or transfer each other by using 001 and 002 if you set Centrex to 3.<br />
<br />
Note, This does not work if you have numbers in different blocks.<br />
<br />
==Permanently Redirecting Calls==<br />
You can permanently redirect an AAISP VoIP number to another number. This could be a mobile or any other number. You may wish to do this in the case of being out of the country or away from your phone. There would be charges for the call from us to the number you are redirecting to.<br />
<br />
For more details on this, see:<br />
*[[VoIP How to: Redirect to another number]]</div>Daggerhttps://support.aa.net.uk/index.php?title=VoIP_-_CDRs&diff=15239VoIP - CDRs2021-07-09T17:35:23Z<p>Dagger: Update links, remove the Other VoIP Features section because it doesn't seem relevant to the page and it's not working anyway</p>
<hr />
<div>__NOTOC__<indicator name="Configuring">[[File:Menu-cog.svg|link=:Category:VoIP Features|30px|Back up to the VoIP Features Category]]</indicator><br />
=Call Detail Records=<br />
<br />
Call Detail Records (CDRs) are available on the Control Pages. The invoice will include an itemised bill too.<br />
<br />
Note that outbound calls to Freephone numbers (e.g. 0800) will not be shown.<br />
<br />
{{CPbox|#Click on, or search for, the number you want to view<br />
#Click on the CDR link to view the Call records<br />
}}<br />
==Fields on the CDR page==<br />
<br />
*Calls in green are outbound calls from the customer<br />
*Calls in blue are inbound calls to the customer<br />
*Calls in white/grey are calls that did not connect<br />
<br />
<br />
<br />
*Ring - the time in seconds the call rang for<br />
*Call - The time in seconds the call lasted for after being answered.<br />
**When a call is not connected, the [https://en.wikipedia.org/wiki/List_of_SIP_response_codes SIP response code] is given in place of the call length. e.g., 180, 183 etc.<br />
*Rate - the [https://www.aa.net.uk/voice-and-mobile/prices/call-prices/ rate code] of the call, e.g. 01 is a UK 01 number, fm are mobile numbers<br />
<br />
[[Category:VoIP Features]]<br />
[[Category:VoIP Logging]]</div>Daggerhttps://support.aa.net.uk/index.php?title=IPv6_Routers&diff=1294IPv6 Routers2012-06-19T14:11:40Z<p>Dagger: it's != its</p>
<hr />
<div>=Technicolor TG582N=<br />
<br />
The TG582N is AAISPs current ADSL router, it was chosen due to its IPv6 support. The Firmware that AAISP use which supports IPv6 is 8.4.7.0.<br />
<br />
The TG582N is a 4 port ADSL router, and can be configured so that one of the ethernet ports can support PPPoE - for connecting to a FTTC Modem. It has wifi too.<br />
<br />
See the [[TG582N]] page for further information, and configuration notes (problems & fixes)<br />
<br />
----<br />
<br />
=Other routers that we've used in the past:=<br />
<br />
<br />
== Billion BiPAC 7800N ==<br />
<br />
Factory IP: 192.168.1.254<br />
Factory User/Pass: admin/admin<br />
<br />
=== Firmware ===<br />
<br />
Latest Firmware is from [http://billion.uk.com/esupport/index.php?/Knowledgebase/Article/View/262/78/bipac-7800n-106d-firmware Billion] As of October 2011 the version we ship is 1.06d <br />
<br />
We have a copy of 1.06d here: <br />
[[media:UKBillion7800NV6_106d.zip]]<br />
<br />
<br />
<br> Another useful Billion page [http://www.spaldwick.com/broadband/billion-7800n on spaldwick.com]<br />
<br />
==Comtrend==<br />
<br />
Info here: *[[Comtrend]]<br />
<br />
==Thomson==<br />
We've tested a TG789vn router (Aug 2011) which had beta IPv6 firmware (10.1.0.3), and this works.<br />
A bit more info here:<br />
[http://revk.www.me.uk/2011/08/ipv6-routers-thomson-step-up-their-game.html]<br />
<br />
==Apple Airport Extreme==<br />
<br />
The Airport Extreme claims to support native IPv6 over PPPoE but we don't know of anyone who has it working. It still works via tunnels though (tunnel configuration explained on the [http://aa.net.uk/kb-broadband-ipv6-tech.html knowledge base]). You need to set the remote tunnel endpoint address to 81.187.81.6, and you need two /64 subnets off us that are statically routed to the Airport's IPv4 address. Assign an IP from one /64 as the WAN address and set the default route to our ping address "bottomless", which is 2001:8b0:0:81::51bb:51bb. Set the LAN address to the first usable IP on the second /64 and it should just work.</div>Dagger