[quote=“pbrunnen”]Don,
Ah… ok… so asterisk is sending the call to the analog station gateway via SIP trunking… got it. Yea… I would concur that it seems to be with your gateway. In your SIP conversation, you see asterisk sending the SIP INVITE to your gateway. The gateway responds first with a TRYING and then a BUSY.
My first recommendation would be to go and look if there is a bug like this reported at the mediatrix manufacurer’s knowledge base.
Second would be to check if there is a firmware upgrade. It might be a software glitch in the gateway.
Last, I would suggest attempting to see if it is your analog phone lines. I am not sure how close your phones are to the gateway or what type of cabling you are using… But next time you can catch a 486 Busy reply, try to unplug (or short out) the analog phone and immediately retry the call. Going back to old school telco stuff here, I wonder if your lines are resetting after the loop opens (e.g. on-hook after a phone call).
Another thought that just poped into my head… check your line signalling on your gateway. This is something that I find gets messed up by softswitch eqipment pretty often. A station should be using a loop start signalling type. In asterisk with digium cards I found that you have to use kewl start rather than loop start, which does not make much sense to me… so this could be something similar.
Hope that helps. -Cheers, Peter.[/quote]
Thanks pburnnen!
As per your message, I called Mediatrix in order to have more info on that matter… We’re doing some ongoing test as we speak…
But in the meantime, I configured a second server, so that some of the calls go through that second server and then to destination. So I had to register the second server as a peer. Everything worked fine. But then, all of a sudden, I was testing that server one more time, and I see that 486 Busy Here error message in CLI! … That’s strange, it means that every registered peers might give me this error… it also means that the problem doesn’t reside in my gateways
… Here, I post my CLI result as well as my debug just in case someone would know…
CLI:
localhostCLI>
– Accepting call from ‘’ to ‘7821627’ on channel 0/2, span 2
localhostCLI>
– Executing NoCDR(“Zap/26-1”, “”) in new stack
localhostCLI>
Nov 15 18:07:35 WARNING[1135]: cdr.c:443 ast_cdr_free: CDR on channel ‘Zap/26-1’ not posted
ocalhostCLI>
– Executing Dial(“Zap/26-1”, “SIP/5147821627@172.16.2.5”) in new stack
localhostCLI>
– Called 5147821627@172.16.2.5
localhostCLI>
– Got SIP response 486 “Busy Here” back from 172.16.2.5
localhostCLI>
– SIP/172.16.2.5-22c2 is busy
localhostCLI>
== Everyone is busy/congested at this time (1:1/0/0)
localhostCLI>
== Spawn extension (macro-CAMBRIDGE_INCOMING, s, 64) exited non-zero on ‘Zap/30-1’ in macro 'CAMBRIDGE_INCOMING’
localhostCLI>
– Hungup ‘Zap/30-1’
SIP DEBUG:
localhostCLI> sip debug peer remote-site
localhostCLI> SIP Debugging Enabled for IP: 172.16.2.5:5060
localhostCLI> – Accepting call from ‘’ to ‘7821627’ on channel 0/21, span 2
localhostCLI> – Executing NoCDR(“Zap/45-1”, “”) in new stack
localhostCLI> Nov 15 17:29:40 WARNING[19428]: cdr.c:443 ast_cdr_free: CDR on channel ‘Zap/45-1’ not posted
localhostCLI> Nov 15 17:29:40 WARNING[19428]: cdr.c:445 ast_cdr_free: CDR on channel ‘Zap/45-1’ lacks end
localhostCLI> – Executing Dial(“Zap/45-1”, “SIP/5147821627@172.16.2.5”) in new stack
localhostCLI> We’re at 172.16.2.4 port 10744
Adding codec 0x4 (ulaw) to SDP
Adding non-codec 0x1 (telephone-event) to SDP
14 headers, 10 lines
Reliably Transmitting (no NAT) to 172.16.2.5:5060:
INVITE sip:5147821627@172.16.2.5 SIP/2.0
Via: SIP/2.0/UDP 172.16.2.4:5060;branch=z9hG4bK6ba6da32;rport
From: “asterisk” sip:asterisk@172.16.2.4;tag=as3ffaaf2f
To: sip:5147821627@172.16.2.5
Contact: sip:asterisk@172.16.2.4
Call-ID: 050ecd7120295cca31a693623f97ad6e@172.16.2.4
CSeq: 102 INVITE
User-Agent: Connect
Max-Forwards: 70
Remote-Party-ID: “asterisk” sip:asterisk@172.16.2.4;privacy=full;screen=pass
Date: Wed, 15 Nov 2006 22:29:40 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 212
v=0
o=root 31058 31058 IN IP4 172.16.2.4
s=session
c=IN IP4 172.16.2.4
t=0 0
m=audio 10744 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
----- Called 5147821627@172.16.2.5
localhost*CLI>
<-- SIP read from 172.16.2.5:5060:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.16.2.4:5060;branch=z9hG4bK6ba6da32;received=172.16.2.4;rport=5060
From: “asterisk” sip:asterisk@172.16.2.4;tag=as3ffaaf2f
To: sip:5147821627@172.16.2.5
Call-ID: 050ecd7120295cca31a693623f97ad6e@172.16.2.4
CSeq: 102 INVITE
User-Agent: Quintum/1.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Contact: sip:5147821627@172.16.2.5
Content-Length: 0
— (10 headers 0 lines)—
localhost*CLI>
<-- SIP read from 172.16.2.5:5060:
SIP/2.0 486 Busy Here
Via: SIP/2.0/UDP 172.16.2.4:5060;branch=z9hG4bK6ba6da32;received=172.16.2.4;rport=5060
From: “asterisk” sip:asterisk@172.16.2.4;tag=as3ffaaf2f
To: sip:5147821627@172.16.2.5;tag=as670846f4
Call-ID: 050ecd7120295cca31a693623f97ad6e@172.16.2.4
CSeq: 102 INVITE
User-Agent: Quintum/1.0.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Contact: sip:5147821627@172.16.2.5
Content-Length: 0
X-Asterisk-HangupCause: No route to destination
— (11 headers 0 lines)—
localhost*CLI>
– Got SIP response 486 “Busy Here” back from 172.16.2.5
Transmitting (no NAT) to 172.16.2.5:5060:
ACK sip:5147821627@172.16.2.5 SIP/2.0
Via: SIP/2.0/UDP 172.16.2.4:5060;branch=z9hG4bK6ba6da32;rport
From: “asterisk” sip:asterisk@172.16.2.4;tag=as3ffaaf2f
To: sip:5147821627@172.16.2.5;tag=as670846f4
Contact: sip:asterisk@172.16.2.4
Call-ID: 050ecd7120295cca31a693623f97ad6e@172.16.2.4
CSeq: 102 ACK
User-Agent: Connect
Max-Forwards: 70
Remote-Party-ID: “asterisk” sip:asterisk@172.16.2.4;privacy=full;screen=pass
Content-Length: 0
----- SIP/172.16.2.5-1c07 is busy
Destroying call ‘050ecd7120295cca31a693623f97ad6e@172.16.2.4’
== Everyone is busy/congested at this time (1:1/0/0)
localhostCLI>
– Channel 0/21, span 2 got hangup request
localhostCLI>
– Hungup ‘Zap/45-1’
It’s very strange… sometimes it’s all good, and some other times I have this error message. I asked to so many person about this problem… it seems like I’m the only person with that issue! … And what’s make it even strangier is that I have the same problem in all of my buildings!
Anyways, if someone has a clue/suggestion/hint… anyting! … I’m all ears…
Thanks alot boys!