SIP Trunk from Provider not Working - Outbound

This site is best viewed in a modern browser with JavaScript enabled.

SIP Trunk from Provider not Working - Outbound

supa

The most straight forward solution is to duplicate the existing trunk for each IP that your provider uses. Only one trunk should have a registration string if using that. That should work for any trunk provider.

If there are a lot of IP's and the trunk provider is sending you a username/password (not necessarily the same as registration string username/password which is for the opposite direction) , an alternative method is to configure Trunks > Trunkname > Incoming Settings that match on username instead of IP. So the PBX is basically acting like an extension for incoming calls.

type=user
username=yourusername
secret=yourpassword
context=from-trunk

When some calls work and some don't this is typically what the problem is. You can tell you have this problem when you call in while watching console and you see "Rejecting unknown SIP connection from xx.xx.xx.xx"

CallCentric suggests another possible way for their service.

/etc/asterisk/sip_custom_post.conf

[alpha1_cc]
type=peer
context=from-pstn
host=alpha1.callcentric.com
 
[alpha2_cc]
type=peer
context=from-pstn
host=alpha2.callcentric.com
 
[alpha3_cc]
type=peer
context=from-pstn
host=alpha3.callcentric.com
 
[alpha4_cc]
type=peer
context=from-pstn
host=alpha4.callcentric.com
 
[alpha5_cc]
type=peer
context=from-pstn
host=alpha5.callcentric.com
 
[alpha6_cc]
type=peer
context=from-pstn
host=alpha6.callcentric.com
 
[alpha7_cc]
type=peer
context=from-pstn
host=alpha7.callcentric.com
 
[alpha8_cc]
type=peer
context=from-pstn
host=alpha8.callcentric.com
 
[alpha9_cc]
type=peer
context=from-pstn
host=alpha9.callcentric.com

seederp2p

Hi Supa,

Thanks for your input. The fact the ITSP is using various IP addresses was an issue with inbound calls that I solved allowing guest calls.

My issue now is the outbound. Sometimes works with ISSABEL and others don't. I don't have any way to know all the IPs they use. The hostnames are always the same. In any case I don't see the problem. What differs from Zoiper to Issabel? :\

supa

Allowing guest calls is not the proper solution imo because it makes your server less secure.

Multiple IP's should not a problem for outbound. Just register with one trunk and one IP. Set hostname to the IP address and not the domain name in outbound settings and registration string.

seederp2p

Already tried that before, setting the ip instead of hostname.

Same behaviour: sometimes it works sometimes it doesn't.

With zoiper softphone the trunk always works.

supa

You can watch SIP traffic to see what happens when it doesn't work.

yum install tcpdump
tcpdump -nqt -s 0 -A host xx.xx.xx.xx and port 5060

Can also try watch from Asterisk console to see if Asterisk is complaining about anything asterisk -vvvr

You did not give any information about your setup. Is Issabel behind NAT? If so did you do all the configurations required on your router and in Issabel for that?

seederp2p

Hi!

I'm behind nat and all the configs are ok.

The packet captures are on the first post.

astbox

Register with the hostname, use it also at the host option and change qualify=yes to qualify=30.
If this doesn't fix your issue try to change the bind port of asterisk to something high enough like 51235.
Doing this will make also your phones unregister so you have to change thei configuration also to the new port.
Chaning the port might help avoid some firwall that might sit on your router distrubing the connection between your box and the provider.

seederp2p

Thanks for your suggestion.

I got this (although I made a call successfully):

OPTIONS sip:proxy.ims.iptv.telecom.pt SIP/2.0
Via: SIP/2.0/UDP 192.168.103.11:5060;branch=z9hG4bK5c9a30b6;rport
Max-Forwards: 70
From: "Unknown" <sip:+22XXXXXXX@192.168.103.11>;tag=as0b60e20a
To: <sip:proxy.ims.iptv.telecom.pt>
Contact: <sip:+22XXXXXXX@192.168.103.11:5060>
Call-ID: 272d8f334720b5986474695077992d92@192.168.103.11:5060
CSeq: 102 OPTIONS
User-Agent: MediaAccess TG789vac v2 Build 10.5.8.I.BQ CP1629UA7MD
Date: Mon, 16 Oct 2017 10:39:16 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<--- SIP read from UDP:213.13.24.193:5060 --->
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.103.11:5060;received=188.83.8.35;branch=z9hG4bK5c9a30b6;rport=62751
From: "Unknown" <sip:+22XXXXXXX@192.168.103.11>;tag=as0b60e20a
To: <sip:proxy.ims.iptv.telecom.pt>;tag=aprqngfrt-tn0t8q00000c6
Call-ID: 272d8f334720b5986474695077992d92@192.168.103.11:5060
CSeq: 102 OPTIONS
P-Charging-Vector: icid-value=b69v1086hpcsioc6ehc83n46ppci6ohemrncmitbjbqe6v054-3;icid-generated-at=213.13.24.193

Maybe I should remove qualify?...

astbox

Xmm, test it. I think the call will fail every time but worth a try.

seederp2p

Removed the qualify and the behaviour is: sometimes it works, sometimes it doesn't... like in the beginning.

supa

If the PBX is behind NAT, where is your public IP in that SIP string? Did you configure Issabel for NAT?

You have to go into unembedded IssabelPBX SIP Settings and set NAT = yes and set your public IP address.

seederp2p

unembedded IssabelPBX I have:

NAT YES
IP Dynamic
Dynamic Host = My hostname that updates dynamically
Local networks = My local networks.

supa

I think Asterisk only resolves DNS hostnames when you reload the configuration. So you can't use it in a dynamic public IP environment if your public IP is constantly changing. If your dynamic IP is not changing I would try set it to static during troubleshooting just to eliminate that possibility.

On your router, make sure SIP ALG is disabled.

seederp2p

the ip doesn't change often... in any case it changes, it's dynamic.

There is no SIP ALG configured.

supa

If the SIP provider does not provide configuration instructions, I just do a google search.

I came up with the following. Looks like maybe you need to set outboundproxy which is one of the more complicated trunk configurations. Outboundproxy then matches via your registration string.

Trunk Name

SOMETRUNKNAME

PEER DETAILS:
username = +3513020 XXXXX
type = friend
t38pt_udptl = yes
secret = PASSWORD_DA_VOSSA_CONTA_VOIP
RegisterName = +3513020 XXXXX
port = 5070
outboundproxy = proxy.voip.sapo.pt
insecure = very
host = proxy.voip.sapo.pt
fromuser = +3513020 XXXXX
from = +3513020 XXXXX
dtmfmode = rfc2833
fromdomain = voip.sapo.pt
disallow = all
allow = ulaw & alaw
context = from-trunk
canreinvite = yes
call-limit = 2
authname = +3513020 XXXXX

+3513020XXXXX:PASSWORD_DA_VOSSA_CONTA_VOIP@SOMETRUNKNAME

The above SOMETRUNKNAME must match the trunk name you set in Issabel just above PEER Details.

seederp2p

I know those configs.

Basically this provider has 2 kinds of services. Nomad numbers (example that you are showing) that are not assigned to any geoprahical zone and geographical numbers (my case). The hostnames are not the same but everything else is pretty much the same.

If you check my first post you'll see that there's already an outboundproxy field...

supa

seederp2p But your registration string does not match mine. So your outboundproxy setting is being ignored. It's a difficult setting to understand properly. Basically, you want the registration string to register to outbound proxy instead of directly to the peer. The only way to do that in Asterisk is to refer it back to the trunk name which then uses outboundproxy setting. With your configuration, when the outbound proxy happens to be the same as the peer, your calls work. But it's not always the same and then the calls fail. The way I showed it is the only way to do it when using outboundproxy as far as I know.

I don't know for sure because I have not used this provider. I have run into this with a few other providers. After spending many hours I finally came up with the config I posted which seems to work reliably.

The other providers that use this are birch.com and voiptalk.org. Google can be very helpful for these things.

https://www.voiptalk.org/products/asterisk-voiptalk-sip-trunk-registration-using-outbound-proxy-setup

seederp2p

I see.

I'm going to test it and will let you know...

markosjal

I had a lot of issues like this with one provider. I had to make both trunkname fields match the assigned username. ALso ensure you have fromuser=(sip username)

seederp2p

If I do this register line like:

+351xxxxxxx: PASSWORD@SOMETRUNKNAME

It breaks the incoming calls: Forbidden - wrong password on authentication for REGISTER for '+35122xxxxxxx to 'MEO'