Strange call

Siemens S450IP.

This morning, around 5 o'clock :-( the phone woke us up. At first I
was going to let it go to voicemail but it kept ringing. Looking at
the display the top line said "No IP" and lower down it said
"asterisk". On answering there was silence. Even odder, on checking
the call log this morning, I have it set to log all, there was nothing
logged. Wife agrees I was not dreaming. :-)

??

--
Regards
Dave Saville

Dave Saville wrote:

> This morning, around 5 o'clock :-( the phone woke us up. At first I
> was going to let it go to voicemail but it kept ringing. Looking at
> the display the top line said "No IP" and lower down it said
> "asterisk". On answering there was silence. Even odder, on checking
> the call log this morning, I have it set to log all, there was nothing
> logged. Wife agrees I was not dreaming. :-)

Does your firewall allow inbound SIP/MGCP sessions from every tom dick
and harry on the internet, or only from your own VoIP provider? If the
former then welcome to the world of SPIT (the IP Telephony equivalent of
SPAM).

On Tue, 21 Dec 2010 21:33:31 UTC, Andy Burns
<usenet.aug2009@adslpipe.co.uk> wrote:

> Dave Saville wrote:
>
> > This morning, around 5 o'clock :-( the phone woke us up. At first I
> > was going to let it go to voicemail but it kept ringing. Looking at
> > the display the top line said "No IP" and lower down it said
> > "asterisk". On answering there was silence. Even odder, on checking
> > the call log this morning, I have it set to log all, there was nothing
> > logged. Wife agrees I was not dreaming. :-)
>
> Does your firewall allow inbound SIP/MGCP sessions from every tom dick
> and harry on the internet, or only from your own VoIP provider? If the
> former then welcome to the world of SPIT (the IP Telephony equivalent of
> SPAM).

Thought it might be - it was the lack of IP address that I could not
work out. But if it uses the IP in the SIP headers rather than the
TCP/IP header I guess that would explain it. Any idea why the call was
not logged?

So for blocking at the firewall I just need to check TCP 5060 is from
the provider?
--
Regards
Dave Saville

Dave Saville wrote:

> it was the lack of IP address that I could not
> work out. But if it uses the IP in the SIP headers rather than the
> TCP/IP header I guess that would explain it. Any idea why the call was
> not logged?

No, I'm not particularly familiar with the Siemens phones, configured a
couple for a friend, but it shouldn't evade logging

> So for blocking at the firewall I just need to check TCP 5060 is from
> the provider?

That should be enough, perhaps 5061 too. With asterisk, MGCP tends to
use a wide range of UDP ports, but for a single phone, it shouldn't get
used until a SIP session calls for it.

Dave Saville explained :
> On Tue, 21 Dec 2010 21:33:31 UTC, Andy Burns
> <usenet.aug2009@adslpipe.co.uk> wrote:
>
>> Dave Saville wrote:
>>
>>> This morning, around 5 o'clock :-( the phone woke us up. At first I
>>> was going to let it go to voicemail but it kept ringing. Looking at
>>> the display the top line said "No IP" and lower down it said
>>> "asterisk". On answering there was silence. Even odder, on checking
>>> the call log this morning, I have it set to log all, there was nothing
>>> logged. Wife agrees I was not dreaming. :-)
>>
>> Does your firewall allow inbound SIP/MGCP sessions from every tom dick
>> and harry on the internet, or only from your own VoIP provider? If the
>> former then welcome to the world of SPIT (the IP Telephony equivalent of
>> SPAM).
>
> Thought it might be - it was the lack of IP address that I could not
> work out. But if it uses the IP in the SIP headers rather than the
> TCP/IP header I guess that would explain it. Any idea why the call was
> not logged?
>
> So for blocking at the firewall I just need to check TCP 5060 is from
> the provider?

You shouldn't need any ports open at all (unless you're using remote
extensions off your own asterisk server, as an example)