Hi, I got a gateway with 4 FXS and 4 FXO.
I can register them one by one with Asterisk sip.conf.
4 FXS (8000-8003) and 4 FXO (8004-8007):
sip show peers
Name/username Host Dyn Forcerport ACL Port Status
8000/8000 192.168.1.104 D A 5060 Unmonitored
8001/8001 192.168.1.104 D A 5060 Unmonitored
8002/8002 192.168.1.104 D A 5060 Unmonitored
8003/8003 192.168.1.104 D A 5060 Unmonitored
8004/8004 192.168.1.104 D A 5060 Unmonitored
8005/8005 192.168.1.104 D A 5060 Unmonitored
8006/8006 192.168.1.104 D A 5060 Unmonitored
8007/8007 192.168.1.104 D A 5060 Unmonitored
== Using SIP RTP CoS mark 5
– Executing [987766788@users:1] Dial(“SIP/801-00000014”, “SIP/8007/87766788”) in new stack
== Using SIP RTP CoS mark 5
– Called SIP/8007/87766788
– SIP/8007-00000015 is circuit-busy
== Everyone is busy/congested at this time (1:0/1/0)
– Auto fallthrough, channel ‘SIP/801-00000014’ status is ‘CONGESTION’
[quote=“javaone9”]For dialing out, how to tell asterisk to use any available FXO?
[/quote]
For real FXOs, you use groups in chan_dahdi.conf.
The best SIP solutions would depend on the gateway doing the hunting. As one gateway handles two logical trunks, this may be difficult. Otherwise you have to treat things as individual extensions, and have your dialplan try each in turn, checking hangup cause to see if the call failed through something that would indicate a busy trunk member, rather than a busy destination.
Your first problem is with the gateway, although capturing a SIP trace of the value of ${HANGUPCAUSE} may indicate a more precise reason for the failure.
For FXO in gateway that is registered as SIP, does it use dadhi?
is it the same as FXO in analog card?
Since there was no error in the gateway log, possiblly configuration issue in
asterisk side? I did not change other configuration files except sip.conf and extensions.conf,
registering FXO/FXS for the gateway.
capturing a SIP trace of the value of ${HANGUPCAUSE}
I am new to asterisk. how to capture the value?
Your FXO in SIP is a remote SIP back to back user agent to Asterisk, which is why hunting needs to done there. Dahdi is not involved. Askterisk has no idea that it contains an FXO interface.
To capture hangup cause add a dialplan line after the one that calls Dial, that runs Noop(HANGUP CAUSE=${HANGUPCAUSE})
Make sure that it has a consecutive priority number. If the dialplan uses n, use n, otherwise you will need to do some renumbering.
Set verbosity to at least 3, with core set verbose 3.
To get a SIP trace, using something like wireshark, or use sip set debug on (the latter would be needed for a formal bug report).
sip show peers
8007/8007 192.168.1.104 D A 5060 Unmonitored
extensions.conf
[incoming]
exten => s,1,Dial(SIP/801,20)
When calling into the FXO 4, I expected to see some output from CLI, and dialed the SIP/801.
but nothing happened. Do I need to do anything else with the gateway?
I changed s to 8007. no luck.
no error message from CLI, nothing.
the gateway FXO 4(SIP/8007) is conntected to PBX(tranditional) extension 603.
When I dialed 603 from another extension 608, I heard ringing tone. but nothing happened.
no messages.
I made some progress. I used the following IP address instead of SIP registration.
gateway ip: 192.168.1.104.
I like to put calls from fxo and fxs into different context. In the gateway router:
FXO X. ROUTE IP 192.168.1.22:5060
FXS X. ROUTE IP 192.168.1.22:5061