Skip to main content

Problems with outgoing calls

Posted by Had on Thu, 10/23/2008

Hello,

I have 2 asterisk systems. Trixbox behind NAT and Thirdlane Multi tenant with public IP address. I have 2 SIP trunks from 2 different provides. I setup the SIP trunks from you on Trixbox system without problems. All incoming and outgoing calls are working fine. But when I setup the trunk on the Thirdlane system the same way only incoming calls are OK. Outgoing calls are not working at all. Always when I try to dial out I get busy tone and the softphone gives me error message "Remote party decline". Is there some special setup for trunks on your system? Do you have some guide how to setup the trunk on your multitenant system?

Regards

Peter


Submitted by justdave on Fri, 10/24/2008 Permalink

Does your SIP provider have your account locked to your IP or do they require you to register? If the latter, have you filled in the registration line near the bottom of the SIP Trunk setup in Thirdlane? Calling party declines on a SIP trunk is usually a bad password or a bad source IP.

Submitted by Had on Sat, 10/25/2008 Permalink

I managed to sort out the problem with outgoing calls. It looks some of the files were corrupted. I reinstalll asterisk and setup everything again and it work ok now. But I have new problem with these SIP trunks...

I have 3 SIP trunks from 3 different providers. When I setup only one of these trunks (any) it will register quickly. When I setup 2 of them, both will register but it takes much longer time. And when I register all 3 they won't register at all, not even 1 of them.

Any idea why?

Submitted by justdave on Mon, 10/27/2008 Permalink

Never seen that before. Can't think of any reason the number of providers would matter, either. I've got 6 trunks defined on my main box, and 2 of those are even two different accounts at the same provider, and mine all register right away during startup. Maybe someone else has an idea.

Submitted by Had on Mon, 10/27/2008 Permalink

this is like neverending story... I managed to sort out that problem, but I have another one.

When I ring my number from first provider it rings on my extension 101 and on the display it shows the number which I call. But when I ring my other SIP providers number it shows number of my mobile phone which I call from which is correct. In the system there is only 1 incomming route setup for all providers, all the incomming calls rings on the same ext 101 and all the SIP trunks are setup exactly the same way. Is that a problem with SIP provider or setup of the trunk on thirdlane box???

Submitted by mattdarnell on Tue, 10/28/2008 Permalink

The best way to check that is to look at the invite message from the carrier in question. It will have all the details.

-Matt

Submitted by eeman on Tue, 10/28/2008 Permalink

if you are getting the wrong CALLERID(num) it is either

a) as a result of information you received from the carrier

b) you incorrectly have callerid defined in the sip trunk in which case you either dont define callerid or define it as callerid=asreceived

Submitted by Had on Wed, 10/29/2008 Permalink

thank you guys for your help.

In the guide from SIP provider for setting-up the SIP trunk it says the caller ID 'must' be set as the DID number from the provider. When it's like that, it shows still the same number for every incomming call comming through that SIP trunk.

So all I needed to do was to delete the caller ID from SIP trunk setting and now when it's blank everything works ok.

Peter

Submitted by justdave on Wed, 10/29/2008 Permalink

They probably meant the outgoing callerid, which would be the one you set in the defaults for new extensions or on each extension.