Un identified SIP registration to Voip Provider .

[kamirie]

Good Day,

I would like to ask what may cause multiple registratios from asterisk to our voip provider , as per voip support , they are seeing multiple registrations from our server's IP , where when I checked I only have 1 carrier configuration to their server. And the other registrations are being show un CLI with random number user id's or 0000000 like this line. I'm chasing my voip provider as SIP registration to their server usualy disconnects and time's out re trying . It will take like 2min - 5min before it can register again and it's affecting the calls. This problem only happens on that single provider. I dont have any problems on other carriers that are being used in the same server

Code: Select all

"F=sip:0000000000@sip.bluepackets.com.au"

Acount Entry

Code: Select all

[BPSIP]
username=xxxxxxxxx
type=friend
secret=xxxxxxxxx
qualify=yes
insecure=port,invite
host=sip.bluepackets.com.au
fromdomain=sip.bluepackets.com.au
disallow=all
allow=alaw
allow=ulaw

Dial Pattern

Code: Select all

exten => _3XXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _3XXXXXXXXX,2,Dial(SIP/BPSIP/0${EXTEN:1},,tTor)
exten => _3XXXXXXXXX,3,Hangup

exten => _3XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _3XXXXXXXXXX,2,Dial(SIP/BPSIP/${EXTEN:1},,tTor)
exten => _3XXXXXXXXXX,3,Hangup

[williamconley]

I've never heard such an issue in the past. But I must caution that you should have a solid "whitelist only" firewall in place on the off-chance that someone is trying to hack your server and pass calls through that provider.

Please post the ACTUAL output and command that you used to get that output to avoid "I thought you meant something else!" problems. Obviously you can replace your IP (and/or the carrier's IP) with a fake. But when you do, always use the same fake for YOU and another same fake for THEM (ie: 8.8.8.8 is you and 4.4.4.4 is them). Same with any passwords/usernames (put in 1234 or abcd instead).

While I see your diaplan, that's entirely unrelated. The registration entry for the carrier, however, is very related and missing. Please post it (with proper replacements) plus "where you put it" (page/field ...?).

Have you modified any of the .conf files manually? ANY of them?

[kamirie]

Hi william ,

Thanks for the reply , Our server's public IP is not accessible outside and firewall system is working as it should .

Surprisingly , I cannot re-create the issue to that voip provider at the moment . I'm not sure why that is but the campaign is on a holliday and that certain carrier is not being used today. I tried to disabled the carrier entry for that by changing active = no in the Carriers page . I waited till a cannot see it from "sip show registry" and "sip show peers" before I enabled it again. But after enabling it , the Sip registered outright to their server unlike last thursday that when we experienced the issue.

Account Entry > setup via vicidial/admin.php > Carriers

Code: Select all

[BPSIP]
username=abcdef
type=friend
secret=12345
qualify=yes
insecure=port,invite
host=sip.bluepackets.com.au
fromdomain=sip.bluepackets.com.au
disallow=all
allow=alaw
allow=ulaw

registration string : register => abcdef:12345@sip.bluepackets.com.au

I didn't change anything on .conf files. I always do cahnges in the vicidial webpages

[williamconley]

Our server's public IP is not accessible outside and firewall system is working as it should .

1) If your server can dial a carrier (and you can receive inbound calls, especially without registration on some accounts), then the server's public IP is accessible outside. Unless your carrier is on your private network. The question then becomes HOW accessible it is. Thus begins the discussion of the firewall.

2) "working as it should" is vague. Is it a whitelist based system?

Not to be argumentative, but I've been down this road a few times. And when you wake up at 6AM on a Sunday to an email from your carrier about the $8k you spent in the last four hours ... it's too late to call PoundTeam and save that money. The carrier is never forgiving. LOL