MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "SPA122",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "90": {
                "pageid": 90,
                "ns": 0,
                "title": "Routers",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Not all NAT firewall/routers can handle voice traffic properly. Symptoms of this include inability to receive calls inbound, dropped calls and no one being able to hear caller when placing an outbound call. Most firewall/router devices have firmware upgrades available to deal with SIP properly, so its always good measure to upgrade to the latest stable firmware.<br> \n\n'''Note:''' Many older devices have no updated firmware and may need to be replaced.\n\n* AOpen Broadband Routers Work fine.\n\n* Cisco PIX 501 - 525 Version 6.3 firmware and greater works with or without SIP handling enabled.\n\n* Cisco IOS with SIP CBAC disabled\n\n* D-Link DI-604 and friends have some problems with early NAT timeouts, causing temporary failures.\n\n* Linksys WRT54G Hardware version 5 requires new firmware immediately after being removed from its box.Version 4 and older are fine.\n\n* Linksys WRT54C All versions appear to work fine.\n\n* Linksys WRT54GS (non SRX model) All versions appear to work fine.\n\n* Linksys SRX gear (all models thus far) cause registration problems with Sipura/PAP2 devices. NAT keep alive fails which results in loss of inbound calling.\n\n* Linux IPTables Works fine, sometimes needs higher UDP timeout setting, but not normally\n\n* OpenBSD software firewalls (FreeBSD works fine, OpenBSD loses NAT sessions)\n\n* SPA-2100/SPA-2102 as a router by itself works fine (with other VoIP behind it)\n\n* TP-LINK TL-WR641G and TL-WR642G works fine.\n\n* Windows 2000/2003/XP Firewall/NAT- Not a good thing, introduces extreme jitter into the stream, but works"
                    }
                ]
            },
            "154": {
                "pageid": 154,
                "ns": 0,
                "title": "SPA1001",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[File:Spa1001.jpg|250px|thumb|]]<br>\nThe SPA-1001 features VoIP adapter functionality found in the SPA-1001 with the additional benefit of an integral connection for legacy telephone network \"hop-on, hop-off\" applications. SPA-1001 users will be able to leverage their broadband phone service connections more than ever by automatically routing local calls from cell phones and land lines to a VoIP service provider and vice versa.\n\nA typical user calling from a land line or mobile phone will be able to reduce and even eliminate international and long distance telephone charges by first calling their SPA-1001 via a local phone number or by using a telephone connected directly to the unit. The advanced authentication and call routing intelligence programmed into the SPA-1001 will connect the caller via the Internet to the far end destination with security and ease. Using the SPA-1001 at the far end, calls can be answered immediately or further processed as a local call to any legacy land line or mobile phone allowed by the SPA-1001 dial plan.\nIf power is lost to the unit or the VoIP service is down, calls can be sent to a traditional carrier via the FXO interface.\n\n'''Note:''' We have seen instances where installing the SPA-1001 behind a firewall which blocks ICMP packets causes problems with registration. Try turning off any ICMP blocking on your firewall.\n\n== How to configure your phone ==\n\n'''1. Find your ATA's IP address'''<br>\nYou must first determine what IP address it received.<br> \n To do this follow next steps:\n Pick up the phone attached to the '''Line 1 jack''' and\n Dial: '''****''' (four asterisks)\n Then dial: '''110 #'''\n Device will play you the assigned IP address (e.g. '''192.168.0.100''')\n\n'''2. Access ATA's Web User Interface'''<br>\nGo to any browser equipped computer on your network and enter the address:<br>\n '''http://<IP_ADDRESS>/'''<br>\n ''(where <IP_ADDRESS> is replaced by the address that was given to you at previous step.''\n\n'''3. Configure device'''<br>\nClick on the \"'''Admin Login'''\" button near the top right side of the screen, then click on the \"'''Line 1'''\" tab.<br>\n [[File:Sipura-spa-1001-config0.gif]]\n\nYou need to modify only a few parameters from the factory default. They are listed here:\n Proxy: '''sip.voicemailtel.net'''\n User ID: '''Enter the user name provided by VoiceMailTel'''\n Password: '''Enter the password provided by VoiceMailTel'''\n Auth ID: ''the same as \"User ID\"''\n Register Expires:'''3600'''\n [[File:Sipura-spa-1001-config1.gif]]\n\n'''4. NAT/Firewall Issues'''<br>\nIf you get one-way audio, you are probably behind NAT. Make the following changes on LINE 1 (you have to click on advanced view to see these options) on the SIP menu.<br>\n [[File:Sipura-spa-1001-config-nat1.gif]]<br>\n [[File:Sipura-spa-1001-config-nat2.gif]]\n\n'''5. Save settings and restart device'''"
                    }
                ]
            }
        }
    }
}