VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
November 2013
- 25 participants
- 69 messages
Adtran TA900 timing problems
by myaklin@g4.net
I have also not been seeing such a problem with an almost identical
setup.
I am using a 7206VXR with PA-MC-2T3+. Two port DS3 card, clear or
channelized running c7200-js-mz.123-3a.bin. The DS3 is using internal
timing. It is channelized.
My DS3 goes from the router to an Adtran M13 mux (MX2820 with a M13 card).
That Adtran M13 mux card gets it's timing from the loop.
As an example of a flawlessly working Adtran hanging off the DS3 is a:
Total Access 916 (1st Gen)
A2.04.00.E
We also use the FXS ports on this box.
On the TA916:
The primary clock source is t1 0/1.
The secondary clock source is t1 0/2 (we do not have a 2nd t1 installed).
We do not set the internal at all.
This T1 is carried over our SONET network, other M13 muxes, etc.. which
pretty much all have BITS clocks connected to them for proper network
timing. From the Central Office to the customer premise would either
be a T1 or copper pairs build a T1 (TA3000) leased from Fairpoint.
Only the Cisco to the M13 mux card has an odd timing setup with no
true BITS clock going into them.
How much of the network do you control? I am going to guess you lease
a channelized DS3(s) from an ILEC and then they terminate the leased T1s
into THEIR m13 mux at the central office which come back to you over the
DS3?
Is the cisco router DS3 using internal or line timing?
Do you have a totally different Cisco 7206 with Adtran 9xx devices hanging
off of it then "just work"? You mention other Cisco routers so I am just
wondering if a 9xx is working on them...
Just rambling here... throwing out what I do. It might set off a light
bulb that leads to the fix.
matt
On Mon, 4 Nov 2013, My List Account wrote:
>
> Has anyone ever seen this problem?? I have a good number of TA900s and TA900Es on the other side of a 7206VXR with PA-MC-T3 cards.?? Once every few months SIP accounts in the TA900s that are attached to FXS ports have trouble passing
> audio.? It sounds like the audio stream is On/Off about every 3 seconds.?? The only ?fix? is to change the timing from the T1 to internal or reboot the router which effectively does the same thing.
>
> ?
>
> It never has an effect on PRI/T1 voice, Hosted PBX behind that router, or data traffic behind the router.? We never see a problem with other Cisco routers connected to the same DS3(s) including voice on Cisco 2431-8FXS and 16FXS
> rotuers.?? When the problem happens it will happen to every TA900 or TA900E at the same time on the same DS3.?? It?s always a single random DS3 in the same box.
>
> ?
>
> I?ve had countless tickets open with our DS3/T1 Provider over the years and they always say they see nothing.? Adtran?s only solution so far is to change the timing when it happens.?? One tech suggested we just run internal timing
> all the time but that seems to only work for 31 days.? I?ve completely swapped out the 7200 and the PA-MC-T3 cards.?? I?ve had a JDSU test set on random DS3s for weeks at a time and never seen a problem.
>
> ?
>
> We set up the routers so that the T1 is the Primary and the Internal is secondary.? I suspect that something happens to the primary clock and it fails to the internal clock.? ?When the primary clock becomes available again the TA900
> does not revert back to the T1 clock.? So when we get to around 31 days the internal timing fails and then the problem with the audio happens.?
>
> ?
>
> ?
>
> ?
>
> -Richey
>
>
>
Nov. 4, 2013
Adtran TA900 timing problems
by paul@timmins.net
We've never seen that here. Do you see incrementing errors on either side of the interface? Do you have log entries on the TA900s?
I assume you tested newer (or older) firmware revisions on the TA900s?
On Mon, 11/04/2013 11:24 AM, "My List Account" <mylists at battleop.com> wrote:
>
Has anyone ever seen this problem? I have a good number of TA900s and TA900Es on the other side of a 7206VXR with PA-MC-T3 cards. Once every few months SIP accounts in the TA900s that are attached to FXS ports have trouble passing audio. It sounds like the audio stream is On/Off about every 3 seconds. The only ?fix? is to change the timing from the T1 to internal or reboot the router which effectively does the same thing.
It never has an effect on PRI/T1 voice, Hosted PBX behind that router, or data traffic behind the router. We never see a problem with other Cisco routers connected to the same DS3(s) including voice on Cisco 2431-8FXS and 16FXS rotuers. When the problem happens it will happen to every TA900 or TA900E at the same time on the same DS3. It?s always a single random DS3 in the same box.
I?ve had countless tickets open with our DS3/T1 Provider over the years and they always say they see nothing. Adtran?s only solution so far is to change the timing when it happens. One tech suggested we just run internal timing all the time but that seems to only work for 31 days. I?ve completely swapped out the 7200 and the PA-MC-T3 cards. I?ve had a JDSU test set on random DS3s for weeks at a time and never seen a problem.
We set up the routers so that the T1 is the Primary and the Internal is secondary. I suspect that something happens to the primary clock and it fails to the internal clock. When the primary clock becomes available again the TA900 does not revert back to the T1 clock. So when we get to around 31 days the internal timing fails and then the problem with the audio happens.
-Richey
_______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Nov. 4, 2013
Adtran TA900 timing problems
by mylists@battleop.com
Has anyone ever seen this problem? I have a good number of TA900s and
TA900Es on the other side of a 7206VXR with PA-MC-T3 cards. Once every few
months SIP accounts in the TA900s that are attached to FXS ports have
trouble passing audio. It sounds like the audio stream is On/Off about
every 3 seconds. The only "fix" is to change the timing from the T1 to
internal or reboot the router which effectively does the same thing.
It never has an effect on PRI/T1 voice, Hosted PBX behind that router, or
data traffic behind the router. We never see a problem with other Cisco
routers connected to the same DS3(s) including voice on Cisco 2431-8FXS and
16FXS rotuers. When the problem happens it will happen to every TA900 or
TA900E at the same time on the same DS3. It's always a single random DS3
in the same box.
I've had countless tickets open with our DS3/T1 Provider over the years and
they always say they see nothing. Adtran's only solution so far is to
change the timing when it happens. One tech suggested we just run internal
timing all the time but that seems to only work for 31 days. I've
completely swapped out the 7200 and the PA-MC-T3 cards. I've had a JDSU
test set on random DS3s for weeks at a time and never seen a problem.
We set up the routers so that the T1 is the Primary and the Internal is
secondary. I suspect that something happens to the primary clock and it
fails to the internal clock. When the primary clock becomes available
again the TA900 does not revert back to the T1 clock. So when we get to
around 31 days the internal timing fails and then the problem with the audio
happens.
-Richey
Nov. 4, 2013
looking for advice on international fraud that took place via an Edgemarc 200EW with FXO line installed
by paul@timmins.net
An embedded and charset-unspecified text was scrubbed...
Name: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20131101/897028e5/at…>
Nov. 1, 2013
looking for advice on international fraud that took place via an Edgemarc 200EW with FXO line installed
by myaklin@g4.net
List,
The problem was I missing a check box labeled:
"Limit Inbound to listed Proxies / SIP Servers"
Under the SIP settings page.
This was my first Edgemarc that had the survivability license with
it so it took some playing around to get everything to work. I must
have unchecked it while trying to fix an issue during setup and never
came back to it.
No problem found. Operator error that probably cost G4 $300 bucks
easy on toll charges.
Thank you all for responding. Now I just need a way to get revenge
on the hacker. Anyone have any contacts in the Gaza Strip? :-(
I know this has been discussed here before but why in the world
would a Palestinian be calling Grenada? How does one make money off
that situation. Sigh...
matt at g4.net
On Fri, 1 Nov 2013, Matt Yaklin wrote:
>
> I think you are on the right track.
>
> I was reading the manual just now trying to figure out how
> or where 1001 comes from. Perhaps that does not even matter.
> You could make up anything.
>
> I am just not seeing how I tell this edgemarc box to stop
> allowing it yet short of using a firewall feature that this
> box does not have like the newest 13.x firmware does. Maybe
> it is hidden or people used the pass through rule set.
>
> matt
>
> On Fri, 1 Nov 2013, Paul Timmins wrote:
>
>> Have you tried tossing an unauthenticated call at the edgemarc from outside
>> using a from address of 1001 at edgemarcip? looks like that's what this guy is
>> doing.
>> You're ignoring his registers but you may be allowing invites from an
>> unregistered device.
>>
>> On Fri, 11/01/2013 03:33 PM, Matt?Yaklin?<myaklin at g4.net> wrote:
>> They are not over lapping.
>>
>> The attacker finally bit just a bit ago. I only was running
>> tcpdump on port 5060 on the edgemarc but i captured the SIP
>> traffic for what the attacker is doing. I wish I had setup
>> more.
>>
>>
>> I blocked international via an auth code right now...
>>
>> x.x.139.225 = WAN ethernet port of the Edgemarc.
>>
>> I am going through this now and if anyone can help I would
>> greatly appreciate it. I need to find out why this is happening.
>>
>>
>>
>> -----------------------
>> -----------------------
>> -----------------------
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Cont
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:18:48.788559 176.58.68.20.10181 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> REGISTER sip:x.x.139.225 SIP/2.0
>> To: <sip:1001 at x.x.139.225>
>> From: <sip:1001 at x.x.139.225>;tag=e26e273f
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
>> Call-ID: b161d8122d506908
>> CSeq: 1 REGISTER
>> Contact: <sip:1001 at 176.58.68.20:10181>
>> Expires: 3600
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Cont
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:18:52.786472 176.58.68.20.10181 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> REGISTER sip:x.x.139.225 SIP/2.0
>> To: <sip:1001 at x.x.139.225>
>> From: <sip:1001 at x.x.139.225>;tag=e26e273f
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
>> Call-ID: b161d8122d506908
>> CSeq: 1 REGISTER
>> Contact: <sip:1001 at 176.58.68.20:10181>
>> Expires: 3600
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Cont
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:18:56.794955 176.58.68.20.10181 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> REGISTER sip:x.x.139.225 SIP/2.0
>> To: <sip:1001 at x.x.139.225>
>> From: <sip:1001 at x.x.139.225>;tag=e26e273f
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
>> Call-ID: b161d8122d506908
>> CSeq: 1 REGISTER
>> Contact: <sip:1001 at 176.58.68.20:10181>
>> Expires: 3600
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Cont
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:19:00.899198 176.58.68.20.10181 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> REGISTER sip:x.x.139.225 SIP/2.0
>> To: <sip:1001 at x.x.139.225>
>> From: <sip:1001 at x.x.139.225>;tag=e26e273f
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
>> Call-ID: b161d8122d506908
>> CSeq: 1 REGISTER
>> Contact: <sip:1001 at 176.58.68.20:10181>
>> Expires: 3600
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Cont
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:19:04.809371 176.58.68.20.10181 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> REGISTER sip:x.x.139.225 SIP/2.0
>> To: <sip:1001 at x.x.139.225>
>> From: <sip:1001 at x.x.139.225>;tag=e26e273f
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
>> Call-ID: b161d8122d506908
>> CSeq: 1 REGISTER
>> Contact: <sip:1001 at 176.58.68.20:10181>
>> Expires: 3600
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Cont
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:19:08.831073 176.58.68.20.10181 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> REGISTER sip:x.x.139.225 SIP/2.0
>> To: <sip:1001 at x.x.139.225>
>> From: <sip:1001 at x.x.139.225>;tag=e26e273f
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
>> Call-ID: b161d8122d506908
>> CSeq: 1 REGISTER
>> Contact: <sip:1001 at 176.58.68.20:10181>
>> Expires: 3600
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Cont
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:19:12.827515 176.58.68.20.10181 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> REGISTER sip:x.x.139.225 SIP/2.0
>> To: <sip:1001 at x.x.139.225>
>> From: <sip:1001 at x.x.139.225>;tag=e26e273f
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
>> Call-ID: b161d8122d506908
>> CSeq: 1 REGISTER
>> Contact: <sip:1001 at 176.58.68.20:10181>
>> Expires: 3600
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Cont
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:19:16.827669 176.58.68.20.10181 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> REGISTER sip:x.x.139.225 SIP/2.0
>> To: <sip:1001 at x.x.139.225>
>> From: <sip:1001 at x.x.139.225>;tag=e26e273f
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
>> Call-ID: b161d8122d506908
>> CSeq: 1 REGISTER
>> Contact: <sip:1001 at 176.58.68.20:10181>
>> Expires: 3600
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Cont
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:23:19.307756 176.58.68.20.10189 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> BYE sip:14734050085 at x.x.139.225:5060 SIP/2.0
>> To: <sip:14734050085 at x.x.139.225>;tag=6516fea2
>> From: <sip:1001 at x.x.139.225>;tag=214bbc47
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10189;branch=z9hG4bK-d87543-1012476641-1--d87543-;rport
>> Call-ID: 346c8a3823657575
>> CSeq: 2 BYE
>> Route: <sip:14734050085 at x.x.139.225;lr>
>> Contact: <sip:1001 at 176.58.68.20:10189>
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE,
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:23:19.370269 x.x.139.225.5060 > 176.58.68.20.10189:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> SIP/2.0 200 OK
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10189;branch=z9hG4bK-d87543-1012476641-1--d87543-;rport=5060
>> Record-Route: <sip:14734050085 at x.x.139.225;lr>
>> From: <sip:1001 at x.x.139.225>;tag=214bbc47
>> To: <sip:14734050085 at x.x.139.225>;tag=6516fea2
>> Call-ID: 346c8a3823657575
>> CSeq: 2 BYE
>> Contact: <sip:14734050085 at x.x.139.225:5060>
>> User-agent: fxo/1.0
>> Content-Length: 0
>>
>>
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>> [tos 0xb8]
>> 19:23:31.365141 176.58.68.20.10189 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> INVITE sip:14734050088 at x.x.139.225 SIP/2.0
>> To: <sip:14734050088 at x.x.139.225>
>> From: <sip:1001 at x.x.139.225>;tag=d909f80a
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport
>> Call-ID: 2b6a574f323db602
>> CSeq: 1 INVITE
>> Contact: <sip:1001 at 176.58.68.20:10189>
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> Content-Type: application/sdp
>> User-Agent: eyeBeam
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>> 19:23:31.417251 x.x.139.225.5060 > 176.58.68.20.10189:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> SIP/2.0 100 Trying
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport=5060
>> From: <sip:1001 at x.x.139.225>;tag=d909f80a
>> To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
>> Call-ID: 2b6a574f323db602
>> CSeq: 1 INVITE
>> User-agent: fxo/1.0
>> Content-Length: 0
>>
>>
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>> [tos 0xb8]
>> 19:23:36.793012 x.x.139.225.5060 > 176.58.68.20.10189:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> SIP/2.0 180 Ringing
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport=5060
>> Record-Route: <sip:14734050088 at x.x.139.225;lr>
>> From: <sip:1001 at x.x.139.225>;tag=d909f80a
>> To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
>> Call-ID: 2b6a574f323db602
>> CSeq: 1 INVITE
>> Contact: <sip:14734050088 at x.x.139.225:5060>
>> User-agent: fxo/1.0
>> Content-Length: 0
>>
>>
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>> [tos 0xb8]
>> 19:23:36.833967 x.x.139.225.5060 > 176.58.68.20.10189:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> SIP/2.0 200 OK
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport=5060
>> Record-Route: <sip:14734050088 at x.x.139.225;lr>
>> From: <sip:1001 at x.x.139.225>;tag=d909f80a
>> To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
>> Call-ID: 2b6a574f323db602
>> CSeq: 1 INVITE
>> Contact: <sip:14734050088 at x.x.139.225:5060>
>> User-agent: fxo/1.0
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE
>> Content-Type: application/sdp
>> Content-Leng
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>> [tos 0xb8]
>> 19:23:37.060875 176.58.68.20.10189 > x.x.139.225.5060:
>> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
>> ACK sip:14734050088 at x.x.139.225:5060 SIP/2.0
>> To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
>> From: <sip:1001 at x.x.139.225>;tag=d909f80a
>> Via: SIP/2.0/UDP
>> 176.58.68.20:10189;branch=z9hG4bK-d87543-154025872-1--d87543-;rport
>> Call-ID: 2b6a574f323db602
>> CSeq: 1 ACK
>> Route: <sip:14734050088 at x.x.139.225;lr>
>> Contact: <sip:1001 at 176.58.68.20:10189>
>> Max-Forwards: 70
>> User-Agent: eyeBeam release 3007n stamp 17816
>> Content-Length: 0
>>
>>
>> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>>
>>
>> ---------------
>> --------------
>> ------------
>>
>> On Fri, 1 Nov 2013, Jay Hennigan wrote:
>>
>> > On 11/1/13 12:04 PM, Matt Yaklin wrote:
>> >>
>> >> Approx 60-70 calls.
>> >
>> > If more than one overlapping you can rule out the physical FXO
>> port.
>> >
>> > --
>> > Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
>> > Impulse Internet Service - http://www.impulse.net/
>> > Your local telephone and internet company - 805 884-6323 - WB6RDV
>> > _______________________________________________
>> > VoiceOps mailing list
>> > VoiceOps at voiceops.org
>> > https://puck.nether.net/mailman/listinfo/voiceops
>> >
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>
Nov. 1, 2013
looking for advice on international fraud that took place via an Edgemarc 200EW with FXO line installed
by myaklin@g4.net
I think you are on the right track.
I was reading the manual just now trying to figure out how
or where 1001 comes from. Perhaps that does not even matter.
You could make up anything.
I am just not seeing how I tell this edgemarc box to stop
allowing it yet short of using a firewall feature that this
box does not have like the newest 13.x firmware does. Maybe
it is hidden or people used the pass through rule set.
matt
On Fri, 1 Nov 2013, Paul Timmins wrote:
> Have you tried tossing an unauthenticated call at the edgemarc from outside using a from address of 1001 at edgemarcip? looks like that's what this guy is doing.
> You're ignoring his registers but you may be allowing invites from an unregistered device.
>
> On Fri, 11/01/2013 03:33 PM, Matt?Yaklin?<myaklin at g4.net> wrote:
> They are not over lapping.
>
> The attacker finally bit just a bit ago. I only was running
> tcpdump on port 5060 on the edgemarc but i captured the SIP
> traffic for what the attacker is doing. I wish I had setup
> more.
>
>
> I blocked international via an auth code right now...
>
> x.x.139.225 = WAN ethernet port of the Edgemarc.
>
> I am going through this now and if anyone can help I would
> greatly appreciate it. I need to find out why this is happening.
>
>
>
> -----------------------
> -----------------------
> -----------------------
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> User-Agent: eyeBeam release 3007n stamp 17816
> Cont
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:18:48.788559 176.58.68.20.10181 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> REGISTER sip:x.x.139.225 SIP/2.0
> To: <sip:1001 at x.x.139.225>
> From: <sip:1001 at x.x.139.225>;tag=e26e273f
> Via: SIP/2.0/UDP
> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
> Call-ID: b161d8122d506908
> CSeq: 1 REGISTER
> Contact: <sip:1001 at 176.58.68.20:10181>
> Expires: 3600
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> User-Agent: eyeBeam release 3007n stamp 17816
> Cont
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:18:52.786472 176.58.68.20.10181 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> REGISTER sip:x.x.139.225 SIP/2.0
> To: <sip:1001 at x.x.139.225>
> From: <sip:1001 at x.x.139.225>;tag=e26e273f
> Via: SIP/2.0/UDP
> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
> Call-ID: b161d8122d506908
> CSeq: 1 REGISTER
> Contact: <sip:1001 at 176.58.68.20:10181>
> Expires: 3600
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> User-Agent: eyeBeam release 3007n stamp 17816
> Cont
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:18:56.794955 176.58.68.20.10181 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> REGISTER sip:x.x.139.225 SIP/2.0
> To: <sip:1001 at x.x.139.225>
> From: <sip:1001 at x.x.139.225>;tag=e26e273f
> Via: SIP/2.0/UDP
> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
> Call-ID: b161d8122d506908
> CSeq: 1 REGISTER
> Contact: <sip:1001 at 176.58.68.20:10181>
> Expires: 3600
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> User-Agent: eyeBeam release 3007n stamp 17816
> Cont
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:19:00.899198 176.58.68.20.10181 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> REGISTER sip:x.x.139.225 SIP/2.0
> To: <sip:1001 at x.x.139.225>
> From: <sip:1001 at x.x.139.225>;tag=e26e273f
> Via: SIP/2.0/UDP
> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
> Call-ID: b161d8122d506908
> CSeq: 1 REGISTER
> Contact: <sip:1001 at 176.58.68.20:10181>
> Expires: 3600
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> User-Agent: eyeBeam release 3007n stamp 17816
> Cont
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:19:04.809371 176.58.68.20.10181 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> REGISTER sip:x.x.139.225 SIP/2.0
> To: <sip:1001 at x.x.139.225>
> From: <sip:1001 at x.x.139.225>;tag=e26e273f
> Via: SIP/2.0/UDP
> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
> Call-ID: b161d8122d506908
> CSeq: 1 REGISTER
> Contact: <sip:1001 at 176.58.68.20:10181>
> Expires: 3600
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> User-Agent: eyeBeam release 3007n stamp 17816
> Cont
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:19:08.831073 176.58.68.20.10181 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> REGISTER sip:x.x.139.225 SIP/2.0
> To: <sip:1001 at x.x.139.225>
> From: <sip:1001 at x.x.139.225>;tag=e26e273f
> Via: SIP/2.0/UDP
> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
> Call-ID: b161d8122d506908
> CSeq: 1 REGISTER
> Contact: <sip:1001 at 176.58.68.20:10181>
> Expires: 3600
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> User-Agent: eyeBeam release 3007n stamp 17816
> Cont
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:19:12.827515 176.58.68.20.10181 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> REGISTER sip:x.x.139.225 SIP/2.0
> To: <sip:1001 at x.x.139.225>
> From: <sip:1001 at x.x.139.225>;tag=e26e273f
> Via: SIP/2.0/UDP
> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
> Call-ID: b161d8122d506908
> CSeq: 1 REGISTER
> Contact: <sip:1001 at 176.58.68.20:10181>
> Expires: 3600
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> User-Agent: eyeBeam release 3007n stamp 17816
> Cont
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:19:16.827669 176.58.68.20.10181 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> REGISTER sip:x.x.139.225 SIP/2.0
> To: <sip:1001 at x.x.139.225>
> From: <sip:1001 at x.x.139.225>;tag=e26e273f
> Via: SIP/2.0/UDP
> 176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
> Call-ID: b161d8122d506908
> CSeq: 1 REGISTER
> Contact: <sip:1001 at 176.58.68.20:10181>
> Expires: 3600
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> User-Agent: eyeBeam release 3007n stamp 17816
> Cont
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:23:19.307756 176.58.68.20.10189 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> BYE sip:14734050085 at x.x.139.225:5060 SIP/2.0
> To: <sip:14734050085 at x.x.139.225>;tag=6516fea2
> From: <sip:1001 at x.x.139.225>;tag=214bbc47
> Via: SIP/2.0/UDP
> 176.58.68.20:10189;branch=z9hG4bK-d87543-1012476641-1--d87543-;rport
> Call-ID: 346c8a3823657575
> CSeq: 2 BYE
> Route: <sip:14734050085 at x.x.139.225;lr>
> Contact: <sip:1001 at 176.58.68.20:10189>
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE,
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:23:19.370269 x.x.139.225.5060 > 176.58.68.20.10189:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP
> 176.58.68.20:10189;branch=z9hG4bK-d87543-1012476641-1--d87543-;rport=5060
> Record-Route: <sip:14734050085 at x.x.139.225;lr>
> From: <sip:1001 at x.x.139.225>;tag=214bbc47
> To: <sip:14734050085 at x.x.139.225>;tag=6516fea2
> Call-ID: 346c8a3823657575
> CSeq: 2 BYE
> Contact: <sip:14734050085 at x.x.139.225:5060>
> User-agent: fxo/1.0
> Content-Length: 0
>
>
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
> [tos 0xb8]
> 19:23:31.365141 176.58.68.20.10189 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> INVITE sip:14734050088 at x.x.139.225 SIP/2.0
> To: <sip:14734050088 at x.x.139.225>
> From: <sip:1001 at x.x.139.225>;tag=d909f80a
> Via: SIP/2.0/UDP
> 176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport
> Call-ID: 2b6a574f323db602
> CSeq: 1 INVITE
> Contact: <sip:1001 at 176.58.68.20:10189>
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO
> Content-Type: application/sdp
> User-Agent: eyeBeam
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
> 19:23:31.417251 x.x.139.225.5060 > 176.58.68.20.10189:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> SIP/2.0 100 Trying
> Via: SIP/2.0/UDP
> 176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport=5060
> From: <sip:1001 at x.x.139.225>;tag=d909f80a
> To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
> Call-ID: 2b6a574f323db602
> CSeq: 1 INVITE
> User-agent: fxo/1.0
> Content-Length: 0
>
>
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
> [tos 0xb8]
> 19:23:36.793012 x.x.139.225.5060 > 176.58.68.20.10189:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> SIP/2.0 180 Ringing
> Via: SIP/2.0/UDP
> 176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport=5060
> Record-Route: <sip:14734050088 at x.x.139.225;lr>
> From: <sip:1001 at x.x.139.225>;tag=d909f80a
> To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
> Call-ID: 2b6a574f323db602
> CSeq: 1 INVITE
> Contact: <sip:14734050088 at x.x.139.225:5060>
> User-agent: fxo/1.0
> Content-Length: 0
>
>
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
> [tos 0xb8]
> 19:23:36.833967 x.x.139.225.5060 > 176.58.68.20.10189:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP
> 176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport=5060
> Record-Route: <sip:14734050088 at x.x.139.225;lr>
> From: <sip:1001 at x.x.139.225>;tag=d909f80a
> To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
> Call-ID: 2b6a574f323db602
> CSeq: 1 INVITE
> Contact: <sip:14734050088 at x.x.139.225:5060>
> User-agent: fxo/1.0
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE
> Content-Type: application/sdp
> Content-Leng
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
> [tos 0xb8]
> 19:23:37.060875 176.58.68.20.10189 > x.x.139.225.5060:
> >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
> ACK sip:14734050088 at x.x.139.225:5060 SIP/2.0
> To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
> From: <sip:1001 at x.x.139.225>;tag=d909f80a
> Via: SIP/2.0/UDP
> 176.58.68.20:10189;branch=z9hG4bK-d87543-154025872-1--d87543-;rport
> Call-ID: 2b6a574f323db602
> CSeq: 1 ACK
> Route: <sip:14734050088 at x.x.139.225;lr>
> Contact: <sip:1001 at 176.58.68.20:10189>
> Max-Forwards: 70
> User-Agent: eyeBeam release 3007n stamp 17816
> Content-Length: 0
>
>
> <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
>
>
> ---------------
> --------------
> ------------
>
> On Fri, 1 Nov 2013, Jay Hennigan wrote:
>
> > On 11/1/13 12:04 PM, Matt Yaklin wrote:
> >>
> >> Approx 60-70 calls.
> >
> > If more than one overlapping you can rule out the physical FXO port.
> >
> > --
> > Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
> > Impulse Internet Service - http://www.impulse.net/
> > Your local telephone and internet company - 805 884-6323 - WB6RDV
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
> >
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
Nov. 1, 2013
looking for advice on international fraud that took place via an Edgemarc 200EW with FXO line installed
by paul@timmins.net
An embedded and charset-unspecified text was scrubbed...
Name: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20131101/4ded0c9d/at…>
Nov. 1, 2013
looking for advice on international fraud that took place via an Edgemarc 200EW with FXO line installed
by myaklin@g4.net
They are not over lapping.
The attacker finally bit just a bit ago. I only was running
tcpdump on port 5060 on the edgemarc but i captured the SIP
traffic for what the attacker is doing. I wish I had setup
more.
I blocked international via an auth code right now...
x.x.139.225 = WAN ethernet port of the Edgemarc.
I am going through this now and if anyone can help I would
greatly appreciate it. I need to find out why this is happening.
-----------------------
-----------------------
-----------------------
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3007n stamp 17816
Cont
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:18:48.788559 176.58.68.20.10181 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
REGISTER sip:x.x.139.225 SIP/2.0
To: <sip:1001 at x.x.139.225>
From: <sip:1001 at x.x.139.225>;tag=e26e273f
Via: SIP/2.0/UDP
176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
Call-ID: b161d8122d506908
CSeq: 1 REGISTER
Contact: <sip:1001 at 176.58.68.20:10181>
Expires: 3600
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3007n stamp 17816
Cont
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:18:52.786472 176.58.68.20.10181 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
REGISTER sip:x.x.139.225 SIP/2.0
To: <sip:1001 at x.x.139.225>
From: <sip:1001 at x.x.139.225>;tag=e26e273f
Via: SIP/2.0/UDP
176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
Call-ID: b161d8122d506908
CSeq: 1 REGISTER
Contact: <sip:1001 at 176.58.68.20:10181>
Expires: 3600
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3007n stamp 17816
Cont
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:18:56.794955 176.58.68.20.10181 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
REGISTER sip:x.x.139.225 SIP/2.0
To: <sip:1001 at x.x.139.225>
From: <sip:1001 at x.x.139.225>;tag=e26e273f
Via: SIP/2.0/UDP
176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
Call-ID: b161d8122d506908
CSeq: 1 REGISTER
Contact: <sip:1001 at 176.58.68.20:10181>
Expires: 3600
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3007n stamp 17816
Cont
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:19:00.899198 176.58.68.20.10181 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
REGISTER sip:x.x.139.225 SIP/2.0
To: <sip:1001 at x.x.139.225>
From: <sip:1001 at x.x.139.225>;tag=e26e273f
Via: SIP/2.0/UDP
176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
Call-ID: b161d8122d506908
CSeq: 1 REGISTER
Contact: <sip:1001 at 176.58.68.20:10181>
Expires: 3600
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3007n stamp 17816
Cont
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:19:04.809371 176.58.68.20.10181 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
REGISTER sip:x.x.139.225 SIP/2.0
To: <sip:1001 at x.x.139.225>
From: <sip:1001 at x.x.139.225>;tag=e26e273f
Via: SIP/2.0/UDP
176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
Call-ID: b161d8122d506908
CSeq: 1 REGISTER
Contact: <sip:1001 at 176.58.68.20:10181>
Expires: 3600
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3007n stamp 17816
Cont
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:19:08.831073 176.58.68.20.10181 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
REGISTER sip:x.x.139.225 SIP/2.0
To: <sip:1001 at x.x.139.225>
From: <sip:1001 at x.x.139.225>;tag=e26e273f
Via: SIP/2.0/UDP
176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
Call-ID: b161d8122d506908
CSeq: 1 REGISTER
Contact: <sip:1001 at 176.58.68.20:10181>
Expires: 3600
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3007n stamp 17816
Cont
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:19:12.827515 176.58.68.20.10181 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
REGISTER sip:x.x.139.225 SIP/2.0
To: <sip:1001 at x.x.139.225>
From: <sip:1001 at x.x.139.225>;tag=e26e273f
Via: SIP/2.0/UDP
176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
Call-ID: b161d8122d506908
CSeq: 1 REGISTER
Contact: <sip:1001 at 176.58.68.20:10181>
Expires: 3600
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3007n stamp 17816
Cont
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:19:16.827669 176.58.68.20.10181 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
REGISTER sip:x.x.139.225 SIP/2.0
To: <sip:1001 at x.x.139.225>
From: <sip:1001 at x.x.139.225>;tag=e26e273f
Via: SIP/2.0/UDP
176.58.68.20:10181;branch=z9hG4bK-d87543-161690352-1--d87543-;rport
Call-ID: b161d8122d506908
CSeq: 1 REGISTER
Contact: <sip:1001 at 176.58.68.20:10181>
Expires: 3600
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
User-Agent: eyeBeam release 3007n stamp 17816
Cont
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:23:19.307756 176.58.68.20.10189 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
BYE sip:14734050085 at x.x.139.225:5060 SIP/2.0
To: <sip:14734050085 at x.x.139.225>;tag=6516fea2
From: <sip:1001 at x.x.139.225>;tag=214bbc47
Via: SIP/2.0/UDP
176.58.68.20:10189;branch=z9hG4bK-d87543-1012476641-1--d87543-;rport
Call-ID: 346c8a3823657575
CSeq: 2 BYE
Route: <sip:14734050085 at x.x.139.225;lr>
Contact: <sip:1001 at 176.58.68.20:10189>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE,
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:23:19.370269 x.x.139.225.5060 > 176.58.68.20.10189:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP
176.58.68.20:10189;branch=z9hG4bK-d87543-1012476641-1--d87543-;rport=5060
Record-Route: <sip:14734050085 at x.x.139.225;lr>
From: <sip:1001 at x.x.139.225>;tag=214bbc47
To: <sip:14734050085 at x.x.139.225>;tag=6516fea2
Call-ID: 346c8a3823657575
CSeq: 2 BYE
Contact: <sip:14734050085 at x.x.139.225:5060>
User-agent: fxo/1.0
Content-Length: 0
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
[tos 0xb8]
19:23:31.365141 176.58.68.20.10189 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
INVITE sip:14734050088 at x.x.139.225 SIP/2.0
To: <sip:14734050088 at x.x.139.225>
From: <sip:1001 at x.x.139.225>;tag=d909f80a
Via: SIP/2.0/UDP
176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport
Call-ID: 2b6a574f323db602
CSeq: 1 INVITE
Contact: <sip:1001 at 176.58.68.20:10189>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: eyeBeam
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
19:23:31.417251 x.x.139.225.5060 > 176.58.68.20.10189:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP
176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport=5060
From: <sip:1001 at x.x.139.225>;tag=d909f80a
To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
Call-ID: 2b6a574f323db602
CSeq: 1 INVITE
User-agent: fxo/1.0
Content-Length: 0
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
[tos 0xb8]
19:23:36.793012 x.x.139.225.5060 > 176.58.68.20.10189:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP
176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport=5060
Record-Route: <sip:14734050088 at x.x.139.225;lr>
From: <sip:1001 at x.x.139.225>;tag=d909f80a
To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
Call-ID: 2b6a574f323db602
CSeq: 1 INVITE
Contact: <sip:14734050088 at x.x.139.225:5060>
User-agent: fxo/1.0
Content-Length: 0
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
[tos 0xb8]
19:23:36.833967 x.x.139.225.5060 > 176.58.68.20.10189:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP
176.58.68.20:10189;branch=z9hG4bK-d87543-292959825-1--d87543-;rport=5060
Record-Route: <sip:14734050088 at x.x.139.225;lr>
From: <sip:1001 at x.x.139.225>;tag=d909f80a
To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
Call-ID: 2b6a574f323db602
CSeq: 1 INVITE
Contact: <sip:14734050088 at x.x.139.225:5060>
User-agent: fxo/1.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE
Content-Type: application/sdp
Content-Leng
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
[tos 0xb8]
19:23:37.060875 176.58.68.20.10189 > x.x.139.225.5060:
>>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>
ACK sip:14734050088 at x.x.139.225:5060 SIP/2.0
To: <sip:14734050088 at x.x.139.225>;tag=51a346d4
From: <sip:1001 at x.x.139.225>;tag=d909f80a
Via: SIP/2.0/UDP
176.58.68.20:10189;branch=z9hG4bK-d87543-154025872-1--d87543-;rport
Call-ID: 2b6a574f323db602
CSeq: 1 ACK
Route: <sip:14734050088 at x.x.139.225;lr>
Contact: <sip:1001 at 176.58.68.20:10189>
Max-Forwards: 70
User-Agent: eyeBeam release 3007n stamp 17816
Content-Length: 0
<<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<
---------------
--------------
------------
On Fri, 1 Nov 2013, Jay Hennigan wrote:
> On 11/1/13 12:04 PM, Matt Yaklin wrote:
>>
>> Approx 60-70 calls.
>
> If more than one overlapping you can rule out the physical FXO port.
>
> --
> Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
> Impulse Internet Service - http://www.impulse.net/
> Your local telephone and internet company - 805 884-6323 - WB6RDV
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Nov. 1, 2013
looking for advice on international fraud that took place via an Edgemarc 200EW with FXO line installed
by myaklin@g4.net
On Fri, 1 Nov 2013, Monterrosa Santiago wrote:
> Hi, interesting puzzle!
>
> Just trying to figure out your scenario
>
> Have you checked in the CDRs if the originating IP address matches the private IP of the Yealink?
> If not, the hacker could be guessing wisely the Broadsoft authentication password of the Yealink
> devices to register its own device from Internet, then making calls to
> Grenada or wherever destination is allowed.
>
I know that scenario is not the case because the POTS line is on
a legacy voice switch which is TDM based. No SIP.
I clearly see the calls coming into my border switch from the
legacy switch. That means the calls came from the POTS line for
sure.
I just put a 8 digit authorization PIN on the POTS for international
dialing to stop the problem for now and buy me some time.
It really does appear that I am either making a config mistake,
the customer has a physical security issue, or the edgemarc has
a problem with its software to allow an attacker to use the FXO
port in some way...
matt at G4.net
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Matt Yaklin
> Sent: viernes, 01 de noviembre de 2013 10:31 a.m.
> To: voiceops at voiceops.org
> Subject: [VoiceOps] looking for advice on international fraud that took place via an Edgemarc 200EW with FXO line installed
>
>
> Hi all,
>
> I had some toll fraud to Grenada last night which we stopped as soon as we became aware of it. Example numbers being dialed were:
>
> 1-473-405-0085
> 1-473-405-0084
> 1-473-405-0088
>
> Normally I can track down how it happened to figure out who was at fault.
> But this time I am having a hard time.
>
> The customer has two types of service from us. Yealink phones connected to our Broadsoft system with an Edgemarc 200EW installed at the customer premise. They also have some POTS line with us for faxing. One of those POTS lines is connected to the Edgemarc 200EW via the built in FXO port for "Survivability". Meaning if the WAN ethernet port on the Edgemarc has a failure they can at least have one line to dial out on in case of an emergency. That is about the only time it would ever be used except for faxing.
>
> The toll fraud CPN just happens to be that POTS line connected to the Edgemarc. That POTS line is also connected to a very basic fax machine.
>
> In the Edgemarc for that FXO port two stage dialing is disabled in both directions. We had incoming calls on the FXO line being forward to a Yealink phone but that would never function properly due to the customer having a fax line picking up first. Just leftover config during the install where we made an assumption the customer might want it.
>
> The Yealink phones are behind the Edgemarc (NAT) and not reachable via the internet. The Edgemarc is using radius for user auth and has strong passwords set. I cannot find any config in Broadsoft where a user had call forwarding setup or whatever that would cause this. I cannot find any settings in the Edgemarc that would allow this to take place. As in a config mistake.
>
> The Edgemarc is running code Version 11.6.19.
> The Yealink phones are also up2date with the newest code from the vendor's website.
>
> I do not think this fraud was done on site via physical means. It is a school and I just cannot picture a student or faculty having a need to call Grenada.
>
> The Edgemarc does have port 5060 open to the world but it is just a ?proxy?
> I was under the impression that one cannot brute force an account on a proxy device that has no config as such like an asterisk box would. You would be basically brute forcing against Broadsoft in that case?
>
> Either way I am still digging into things but I thought by sending this email someone might have some advice to clue me into something I am missing when it comes to Edgemarc and FXO security.
>
> Thanks,
>
> matt at g4.net
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
> La informaci?n en este correo electr?nico y sus anexos es confidencial y privilegiada. Est? dirigida exclusivamente a sus destinatarios y por lo tanto nadie m?s est? autorizado a tener acceso a ?lla. Si Ud. no es el destinatario, es il?cito imprimirla, reproducirla o distribuirla. Si lo recibi? por error, por favor avise al remitente y borre cualquier registro en sus sistemas.
>
> CONFIDENTIALITY NOTICE: This email message and its attachments, if any, are intended only for the person or entity to which it is addressed and contains privileged information. Any use, printing, disclosure, or distribution of such information without the written authorization is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message.
>
> Nuestro aviso de privacidad est? publicado en la p?gina web: http://www.mcmtelecom.com.mx/common/politica_privacidad.htm
>
>
Nov. 1, 2013
looking for advice on international fraud that took place via an Edgemarc 200EW with FXO line installed
by jay@west.net
On 11/1/13 12:04 PM, Matt Yaklin wrote:
>
> Approx 60-70 calls.
If more than one overlapping you can rule out the physical FXO port.
--
Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
Impulse Internet Service - http://www.impulse.net/
Your local telephone and internet company - 805 884-6323 - WB6RDV
Nov. 1, 2013