Nice, glad it worked :-) Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. moy@sangoma.com On Tue, May 18, 2010 at 12:07 PM, Neil Patel <neilp@cs.stanford.edu> wrote:
Hey Moises,
Upgrading wanpipe and FS to the latest did the trick. Thanks!
-Neil
On Mon, May 17, 2010 at 7:44 AM, Moises Silva <moises.silva@gmail.com>wrote:
Try taking a protocol dump using wanpipemon on the d-channel so we can see the full details of the call setup.
http://wiki.sangoma.com/wanpipe-wireshark-pcap-pri-bri-wan-t1-e1-tracing#pri...
Then paste a link here to the pcap file somewhere.
Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. moy@sangoma.com
On Sun, May 16, 2010 at 8:16 PM, Neil Patel <neilp@cs.stanford.edu>wrote:
Thanks Moises, this is very helpful!
After fixing the dialstring, I am still getting the following error from FS:
originate openzap/smg_prid/a/<num> &echo -ERR NORMAL_CIRCUIT_CONGESTION
2010-05-17 05:39:02.883264 [WARNING] ozmod_sangoma_boost.c:346 TX EVENT: CALL_START:(80) [w1g1] CSid=1 Seq=0 Cn=[FreeSWITCH] Cd=[9428500597] Ci=[0000000000] Rdnis=[] freeswitch@internal> 2010-05-17 05:39:02.955336 [WARNING] ozmod_sangoma_boost.c:1312 RX EVENT (N): CALL_START_NACK:(82) [w256g256] Rc=0 CSid=1 Seq=1 2010-05-17 05:39:02.955336 [WARNING] sangoma_boost_client.c:220 TX EVENT (N): CALL_START_NACK_ACK:(83) [w1g1] Rc=0 CSid=1 Seq=1 2010-05-17 05:39:02.956586 [ERR] mod_openzap.c:1154 No channels available 2010-05-17 05:39:02.956586 [ERR] switch_ivr_originate.c:2249 Cannot create outgoing channel of type [openzap] cause: [NORMAL_CIRCUIT_CONGESTION]
Here is the relevant logging from /var/log/sangoma_mgd.log:
May 17 05:39:02 otalo sangoma_prid: Rx SMG [CALL_START s:0 c:0 id:1] May 17 05:39:02 otalo sangoma_prid: g1:Outgoing call (Smg-ID:1) May 17 05:39:02 otalo sangoma_prid: s1:Outgoing call ChanRq:1 Called-Nb[9428500597] Calling-Nb[0000000000] (Smg-ID:1) May 17 05:39:02 otalo sangoma_prid: Rx Tsoft [7:StatusIn id:0] May 17 05:39:02 otalo sangoma_prid: s1:Received cause-ind-An IE or parameter does not exist(99) May 17 05:39:02 otalo sangoma_prid: Rx Tsoft [2:DiscIn id:0] May 17 05:39:02 otalo sangoma_prid: s1c1:Remote released-Unknown(0) May 17 05:39:02 otalo sangoma_prid: Rx SMG [CALL_START_NACK_ACK s:0 c:0 id:1] May 17 05:39:02 otalo sangoma_prid: g1:Call cleared (SMG-ID:1)
I updated /etc/wanpipe/smg_pri.conf to have group=1 uncommented.
Please note that my box is in India, making calls over a PRI line set up there. I also changed my tones.conf to match what's on the wiki<http://wiki.freeswitch.org/wiki/Tones.conf_Example>for India.
Thanks, Neil
On Sat, May 15, 2010 at 10:20 PM, Moises Silva <moises.silva@gmail.com>wrote:
Hi Again Neil,
I just noticed your dial string is incorrect. The correct syntax is:
OpenZAP/<span>/<chan_code>/[number]
The span and chan code are mandatory. The number is optional ( FXS channels do not require a number, they just ring the FXO device connected to them).
The span is either a number ( span id, the id is a number assigned in the order in which the span is defined in openzap.conf ) or a span name also as specified in the [span wanpipe <span_name>] line in openzap.conf
The chan code is either a number ( for spans that support individual channel selection, boost is NOT one of them ), or a channel hunting mode, there is currently 2 modes, "a" is top down and "A" is bottom up.
So, this is a valid string for you case:
OpenZAP/smg_prid/a/<number>
In the specific case of boost in socket mode ( openzap only supports socket mode ) the number may contain @gX where X is a group ( for hunting as configured in /etc/wanpipe/smg_pri.conf). Boost signaling are a special case because the hunting for channels is not done within FreeSWITCH but in sangoma_prid binary ( in the new OpenZAP version called FreeTDM this has changed depending on configuration).
Bottom line, this should work:
OpenZAP/smg_prid/a/1234@g1
If you have g1 configured in /etc/wanpipe/smg_pri.conf
Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. moy@sangoma.com
On Sat, May 15, 2010 at 6:26 PM, Neil Patel <neilp@cs.stanford.edu>wrote:
Span was originally in the boost section when I got this error, so I thought I'd try it in analog and both. None work.
-Neil
On Sat, May 15, 2010 at 3:18 PM, Moises Silva <moises.silva@gmail.com>wrote:
Why do you have 2 spans in openzap.conf.xml with the same name, in both the boost and analog sections? Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. moy@sangoma.com
On Sat, May 15, 2010 at 3:52 PM, Neil Patel <neilp@cs.stanford.edu>wrote:
> Hi All, > > I am trying to dial out over my PRI, and am getting this error: > > 2010-05-16 01:01:21.452392 [CRIT] zap_io.c:1139 SPAN NOT DEFINED! > 2010-05-16 01:01:21.452392 [ERR] mod_openzap.c:1154 No channels > available > 2010-05-16 01:01:21.452392 [ERR] switch_ivr_originate.c:2249 Cannot > create outgoing channel of type [OpenZAP] cause: [NORMAL_CIRCUIT_CONGESTION] > > > This is my openzap.conf: > > [span wanpipe smg_prid] > name => smg_prid > trunk_type =>e1 > b-channel => 1:1-15 > b-channel => 1:17-31 > trunk_type =>e1 > b-channel => 2:1-15 > b-channel => 2:17-31 > > > This is my openzap.conf.xml: > > <configuration name="openzap.conf" description="OpenZAP > Configuration"> > <settings> > <param name="debug" value="0"/> > > </settings> > <boost_spans> > <span id="smg_prid"> > <param name="dialplan" value="XML"/> > <param name="context" value="default"/> > </span> > </boost_spans> > > <analog_spans> > <span id="smg_prid"> > <param name="dialplan" value="XML"/> > <param name="context" value="default"/> > > </span> > </analog_spans> > </configuration> > > > And here is the lua code I'm using to dial out: > > sessiondata = "OpenZAP/smg_prid/<num>" > new_session = freeswitch.Session(sessiondata) > > > What am I missing here? > Thanks, > Neil > > > > _______________________________________________ > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE: > http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > >
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org