asterisk@dreamwerx.net
2004-Jul-09 07:28 UTC
[Asterisk-Users] vonage.ca * integration possible?
I just got setup with vonage.ca with the motorola ata unit.. I fired up ethreal and checked out what's flying over the network... The sniff below would lead me to believe that it might be possible to have asterisk spoof the User-Agent field and register itself? Any thoughts/feedback? Thanks.> > No. Time Source Destination Protocol Info > 222 53.601179 172.21.5.102 216.115.25.187 SIP Request: REGISTER sip:bspgroup1.bsp.vonage.net:5061 > > Frame 222 (622 bytes on wire, 622 bytes captured) > Ethernet II, Src: 00:0f:9f:86:42:d4, Dst: 00:06:25:db:aa:25 > Internet Protocol, Src Addr: 172.21.5.102 (172.21.5.102), Dst Addr: 216.115.25.187 (216.115.25.187) > User Datagram Protocol, Src Port: 5061 (5061), Dst Port: 5061 (5061) > Session Initiation Protocol > Request-Line: REGISTER sip:bspgroup1.bsp.vonage.net:5061 SIP/2.0 > Method: REGISTER > Resent Packet: False > Message Header > From: <sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;tag=ac150566-13c5-40eca012-eaee0a8-76e4;user=phone > To: <sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;user=phone > Call-ID: ac150566-13c5-40e8ddde-51e6-2327-0 > CSeq: 1 REGISTER > Via: SIP/2.0/UDP 172.21.5.102:5061;branch=z9hG4bK-40eca012-eaee0a8-474d > User-Agent: <Motorola VT1000 mac: 000F9F8XXXXX sw:VT20_1.1.16e ln:0 cfg:10886711XXXXX/10022XXXXX> > Max-Forwards: 70 > Contact: <sip:1905XXXXXXX@172.21.5.102:5061>;user=phone;transport=udp > Expires: 900 > Content-Length:0 > > No. Time Source Destination Protocol Info > 224 53.711988 172.21.5.102 216.115.25.187 SIP Request: REGISTER sip:bspgroup1.bsp.vonage.net:5061 > > Frame 224 (713 bytes on wire, 713 bytes captured) > Ethernet II, Src: 00:0f:9f:86:42:d4, Dst: 00:06:25:db:aa:25 > Internet Protocol, Src Addr: 172.21.5.102 (172.21.5.102), Dst Addr: 216.115.25.187 (216.115.25.187) > User Datagram Protocol, Src Port: 5061 (5061), Dst Port: 5061 (5061) > Session Initiation Protocol > Request-Line: REGISTER sip:bspgroup1.bsp.vonage.net:5061 SIP/2.0 > Method: REGISTER > Resent Packet: False > Message Header > From: <sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;tag=ac150566-13c5-40eca012-eaee0a8-76e4;user=phone > To: <sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;user=phone > Call-ID: ac150566-13c5-40e8ddde-51e6-2327-0 > CSeq: 2 REGISTER > Via: SIP/2.0/UDP 172.21.5.102:5061;branch=z9hG4bK-40eca012-eaee10c-2713 > Max-Forwards: 70 > Contact: <sip:1905XXXXXXX@172.21.5.102:5061>;user=phone;transport=udp > Expires: 900 > Authorization: Digest username="1905XXXXXXX", realm="216.115.25.187", nonce="720170349", uri="sip:bspgroup1.bsp.vonage.net:5061", response="6a2fe5ec7b98a098aaf82a7dfc1340aa", algorithm=MD5 > Content-Length:0 > > No. Time Source Destination Protocol Info > 234 67.817617 172.21.5.102 216.115.25.187 SIP Request: REGISTER sip:bspgroup1.bsp.vonage.net:5061 > > Frame 234 (622 bytes on wire, 622 bytes captured) > Ethernet II, Src: 00:0f:9f:86:42:d4, Dst: 00:06:25:db:aa:25 > Internet Protocol, Src Addr: 172.21.5.102 (172.21.5.102), Dst Addr: 216.115.25.187 (216.115.25.187) > User Datagram Protocol, Src Port: 5061 (5061), Dst Port: 5061 (5061) > Session Initiation Protocol > Request-Line: REGISTER sip:bspgroup1.bsp.vonage.net:5061 SIP/2.0 > Method: REGISTER > Resent Packet: False > Message Header > From: <sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;tag=ac150566-13c5-40eca020-eaf1830-3c4e;user=phone > To: <sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;user=phone > Call-ID: ac150566-13c5-40e8ddde-51e6-2327-0 > CSeq: 1 REGISTER > Via: SIP/2.0/UDP 172.21.5.102:5061;branch=z9hG4bK-40eca020-eaf1830-216f > User-Agent: <Motorola VT1000 mac: 000F9F8XXXXX sw:VT20_1.1.16e ln:0 cfg:1088671XXXXXX/100225XXXX> > Max-Forwards: 70 > Contact: <sip:1905XXXXXXX@172.21.5.102:5061>;user=phone;transport=udp > Expires: 900 > Content-Length:0 > > No. Time Source Destination Protocol Info > 245 76.007450 172.21.5.102 216.115.25.187 SIP/SDP Request: INVITE sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061, with session description > > Frame 245 (972 bytes on wire, 972 bytes captured) > Ethernet II, Src: 00:0f:9f:86:42:d4, Dst: 00:06:25:db:aa:25 > Internet Protocol, Src Addr: 172.21.5.102 (172.21.5.102), Dst Addr: 216.115.25.187 (216.115.25.187) > User Datagram Protocol, Src Port: 5061 (5061), Dst Port: 5061 (5061) > Session Initiation Protocol > Request-Line: INVITE sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061 SIP/2.0 > Method: INVITE > Resent Packet: False > Message Header > From: "905-XXX-XXXX"<sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;tag=ac150566-13c5-40eca028-eaf3828-4f5a;user=phone > To: <sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;user=phone > Call-ID: 9452a300-5225-1089249320-14781852-128603414000366400000000-0@172.21.5.102 > CSeq: 1 INVITE > Via: SIP/2.0/UDP 172.21.5.102:5061;branch=z9hG4bK-40eca028-eaf3828-658b > User-Agent: <Motorola VT1000 mac: 000F9FXXXXXX sw:VT20_1.1.16e ln:0 cfg:10886711XXXXX/10022XXXXX> > Max-Forwards: 70 > Contact: <sip:1905XXXXXXX@172.21.5.102:5061;transport=UDP;user=phone> > Content-Type: application/SDP > Content-Length:270 > Message body > > No. Time Source Destination Protocol Info > 247 76.116876 172.21.5.102 216.115.25.187 SIP Request: ACK sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061 > > Frame 247 (564 bytes on wire, 564 bytes captured) > Ethernet II, Src: 00:0f:9f:86:42:d4, Dst: 00:06:25:db:aa:25 > Internet Protocol, Src Addr: 172.21.5.102 (172.21.5.102), Dst Addr: 216.115.25.187 (216.115.25.187) > User Datagram Protocol, Src Port: 5061 (5061), Dst Port: 5061 (5061) > Session Initiation Protocol > Request-Line: ACK sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061 SIP/2.0 > Method: ACK > Resent Packet: False > Message Header > From: "905-XXX-XXXX"<sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;tag=ac150566-13c5-40eca028-eaf3828-4f5a;user=phone > To: <sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;user=phone > Call-ID: 9452a300-5225-1089249320-14781852-128603414000366400000000-0@172.21.5.102 > CSeq: 1 ACK > Via: SIP/2.0/UDP 172.21.5.102:5061;branch=z9hG4bK-40eca028-eaf3828-658b > Max-Forwards: 70 > Contact: <sip:1905XXXXXXX@172.21.5.102:5061;transport=UDP;user=phone> > Content-Length:0 > > No. Time Source Destination Protocol Info > 248 76.123752 172.21.5.102 216.115.25.187 SIP/SDP Request: INVITE sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061, with session description > > Frame 248 (1181 bytes on wire, 1181 bytes captured) > Ethernet II, Src: 00:0f:9f:86:42:d4, Dst: 00:06:25:db:aa:25 > Internet Protocol, Src Addr: 172.21.5.102 (172.21.5.102), Dst Addr: 216.115.25.187 (216.115.25.187) > User Datagram Protocol, Src Port: 5061 (5061), Dst Port: 5061 (5061) > Session Initiation Protocol > Request-Line: INVITE sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061 SIP/2.0 > Method: INVITE > Resent Packet: False > Message Header > From: "905-XXX-XXXX"<sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;tag=ac150566-13c5-40eca028-eaf3828-4f5a;user=phone > To: <sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061>;user=phone > Call-ID: 9452a300-5225-1089249320-14781852-128603414000366400000000-0@172.21.5.102 > CSeq: 2 INVITE > Via: SIP/2.0/UDP 172.21.5.102:5061;branch=z9hG4bK-40eca029-eaf389c-5a81 > User-Agent: <Motorola VT1000 mac: 000F9FXXXXXX sw:VT20_1.1.16e ln:0 cfg:1088671XXXXXX/10022XXXXX> > Max-Forwards: 70 > Contact: <sip:1905XXXXXXX@172.21.5.102:5061;transport=UDP;user=phone> > Proxy-Authorization: Digest username="1905XXXXXXX", realm="216.115.25.187", nonce="1413734098", uri="sip:1905XXXXXXX@bspgroup1.bsp.vonage.net:5061", response="e40d9ebae8ebb6c901b56cad9dd8d7e0", algorithm=MD5 > Content-Type: application/SDP > Content-Length:270 > Message body > > No. Time Source Destination Protocol Info > 251 79.262346 172.21.5.102 206.132.91.148 RTP Payload type=ITU-T G.711 PCMU, SSRC=5791, Seq=32514, Time=93961680, Mark > > Frame 251 (214 bytes on wire, 214 bytes captured) > Ethernet II, Src: 00:0f:9f:86:42:d4, Dst: 00:06:25:db:aa:25 > Internet Protocol, Src Addr: 172.21.5.102 (172.21.5.102), Dst Addr: 206.132.91.148 (206.132.91.148) > User Datagram Protocol, Src Port: 10000 (10000), Dst Port: 12084 (12084) > Real-Time Transport Protocol > > No. Time Source Destination Protocol Info > 252 79.283170 172.21.5.102 206.132.91.148 RTP Payload type=ITU-T G.711 PCMU, SSRC=5791, Seq=32515, Time=93961840 > > Frame 252 (214 bytes on wire, 214 bytes captured) > Ethernet II, Src: 00:0f:9f:86:42:d4, Dst: 00:06:25:db:aa:25 > Internet Protocol, Src Addr: 172.21.5.102 (172.21.5.102), Dst Addr: 206.132.91.148 (206.132.91.148) > User Datagram Protocol, Src Port: 10000 (10000), Dst Port: 12084 (12084) > Real-Time Transport Protocol > > No. Time Source Destination Protocol Info > 253 79.303180 172.21.5.102 206.132.91.148 RTP Payload type=ITU-T G.711 PCMU, SSRC=5791, Seq=32516, Time=93962000 > > Frame 253 (214 bytes on wire, 214 bytes captured) > Ethernet II, Src: 00:0f:9f:86:42:d4, Dst: 00:06:25:db:aa:25 > Internet Protocol, Src Addr: 172.21.5.102 (172.21.5.102), Dst Addr: 206.132.91.148 (206.132.91.148) > User Datagram Protocol, Src Port: 10000 (10000), Dst Port: 12084 (12084) > Real-Time Transport Protocol >
Your problem with doing this is this line right below...you have no idea what your authentication secret is. This is a closely guarded secret of Vonage. They don't have any interest in letting anyone do this. The closest you could do would be a softphone, unlimited inbound and 500 mins outbound calling. There are sample configs floating around out there to make that work. On Fri, 9 Jul 2004 10:28:06 -0400 (EDT), asterisk@dreamwerx.net <asterisk@dreamwerx.net> wrote:> > Authorization: Digest username="1905XXXXXXX", realm="216.115.25.187", nonce="720170349", uri="sip:bspgroup1.bsp.vonage.net:5061", response="6a2fe5ec7b98a098aaf82a7dfc1340aa", algorithm=MD5
Sure it's possible. It's probably not trivial though -- for one, you'd need to get the password somehow so that you can produce the md5 response. It probably wouldn't be very stable either, since Vonage keeps changing rotating the passwords (did so with the ATA186 at least) at least once a week, and since you're violating their Terms of Use, they may shut you down anytime. However, the Vonage Softphone service works JUST FINE with asterisk, no special hacks required. I have it running with a $15/month hardline and $10/month softphone so I get my incoming calls in a rate-center that nobody else offers.> -----Original Message----- > From: asterisk@dreamwerx.net [mailto:asterisk@dreamwerx.net] > Sent: Friday, July 09, 2004 9:28 AM > To: asterisk-users@lists.digium.com > Subject: [Asterisk-Users] vonage.ca * integration possible? > > > > I just got setup with vonage.ca with the motorola ata unit.. > I fired up ethreal and checked out what's flying over the > network... The sniff below would lead me to believe that it > might be possible to have asterisk spoof the User-Agent field > and register itself? > > Any thoughts/feedback? Thanks.