concurrent SIP trunks registrations fail

artvladi
Posts: 15
Member Since:
2009-11-17

I have 2 SIP trunks and they register fine with 2 different providers as long as they are not enabled at the same time. If I enable them both, the asterisk log shows that both registrations start to time out and never register:

[Nov 17 13:41:38] NOTICE[4036] chan_sip.c: -- Registration for '1777382180218@callcentric.com' timed out, trying again (Attempt #2)

What could be the issue here?

Thank you



jdwebcc
Posts: 149
Member Since:
2006-09-27
Its all in the router !

Try another smarter router.. ! A lot of routers (bought off the shelf) wont allow more than one SIP registration.

JD

--

Jason S Derr, JDWEB.cc LLC
Creator of ASR Manager



artvladi
Posts: 15
Member Since:
2009-11-17
concurrent SIP trunks registrations fail

I have 2 SIP trunks and they register fine with 2 different providers as long as they are not enabled at the same time. If I enable them both, the asterisk log shows that both registrations start to time out and never register:

[Nov 17 13:41:38] NOTICE[4036] chan_sip.c: -- Registration for '1777382180218@callcentric.com' timed out, trying again (Attempt #2)

What could be the issue here?

I confirmed that the issue is NOT with the router. I also set up Asterisk 1.2.26 with the exact same sip accounts and all identical settings on a different PC and it registers both accounts instantly. So, it must be something else in the trixbox config or the newer Asterisk it uses.



artvladi
Posts: 15
Member Since:
2009-11-17
the active channels show a

the active channels show a huge number of active channels that accumulate with every unsuccessful registration attempt:

Active Channel(s)
Peer User/ANR Call ID Format Hold Last Message
0.0.0.0 (None) 4d862237027d85c 0x0 (nothing) No
213.85.168.52 (None) 6045b842030831f 0x0 (nothing) No Init: OPTIONS
204.11.192.36 (None) 00f4f42b5b7e072 0x0 (nothing) No Init: OPTIONS

they all seem to hang after the "Init: OPTIONS" message.



SkykingOH
Posts: 9681
Member Since:
2007-12-17
Post the peer details of

Post the peer details of both trunks or nobody will be able to help you.

--

Scott

aka "Skyking"



artvladi
Posts: 15
Member Since:
2009-11-17
concurrent SIP trunks registrations fail

I have 2 callcentric registrations that work individually, but fail to register when are used at the same time. The same config works just fine with the same router and the astersik 1.2. Here are the peer details:

username=17771234567
type=friend
secret=mypassword
insecure=port,invite
host=callcentric.com
fromuser=17771234567
fromdomain=callcentric.com
defaultuser=17771234567
context=from-pstn
nat=yes

Register string:
17771234567:mypassword@callcentric.com/17771234567

The second peer is the same except the account is different. I tried other VOIP providers with the same effect. So, it must be something with the trixbox config itself.



artvladi
Posts: 15
Member Since:
2009-11-17
concurrent SIP trunks registrations fail

I have 2 callcentric registrations that work individually, but fail to register when are used at the same time. The same config works just fine with the same router and the astersik 1.2. Here are the peer details:

username=17771234567
type=friend
secret=mypassword
insecure=port,invite
host=callcentric.com
fromuser=17771234567
fromdomain=callcentric.com
defaultuser=17771234567
context=from-pstn
nat=yes

Register string:
17771234567:mypassword@callcentric.com/17771234567

The second peer is the same except the account is different. I tried other VOIP providers with the same effect. So, it must be something with the trixbox config itself.



artvladi
Posts: 15
Member Since:
2009-11-17
concurrent SIP trunks registrations fail

The same thing happens when the trixbox is directly connected to the internet or in the DMZ, so it should be easy to reproduce. I wonder if this is a frequently encountered issue with trixbox?



b14ck
Posts: 773
Member Since:
2009-03-03
I've never had an issue. It

I've never had an issue. It sounds like your NAT / networking is messed up. Try sitting the server on a public IP and make sure nat=no is set in your sip.conf and your trunks. Turn the sip debugging on as well, and paste a full call log.

--

Randall Degges
Lead Developer, RCI Telecommunications
projectb14ck - http://projectb14ck.org/ - Weblog



artvladi
Posts: 15
Member Since:
2009-11-17
this is a bug!

Other people suffer from it as well:

https://issues.asterisk.org/view.php?id=15052

You should patch the trixbox ISO with this fix.



artvladi
Posts: 15
Member Since:
2009-11-17
definitely a bug that persists from 1.4!!!

I solved the issue by using a different DNS server in the /etc/resolv.conf

following the advice from:

https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=151...

I wonder why this really stupid C code, that persists for so many years, does not detect the issues with the DNS server and reports totally inappropriate ambiguous messages in the log?



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.