[Freeswitch-users] How to setup a span as PRI_NET

lakshmanan ganapathy lakindia89 at gmail.com
Sat Apr 17 02:12:16 PDT 2010 

Hi all,
         I've contacted the sangoma support, and they are looking into the
issue.
They also told that the problem is in the PRI STACK.
So in the mean time, I planned to change the stack and check. So I switched
to libpri.
I've configured the things and both Incoming and outgoing works on span1.
On span2, from the extension, If I dial, I got

2010-04-17 10:51:15.218100 [WARNING] ozmod_libpri.c:760 --Duplicate Ring on
channel 2:-1 (ignored)

The freeswitch log is:
     http://pastebin.freeswitch.org/12738
I also went to see what is the problem. It seems to me that, when SETUP
comes, ozmod_libpri.c is checking for the B-channel number.
Since it is not there, it print Duplicate ring on channel.

I also came to know that, first SETUP will request the telco (B-chan
identification won't be there). Then the telco responds with the B-channel
to use in SETUP_ACK.
The further communication will happen with the B-chan identification.

Am  I correct!!. Please give inputs to me to solve this issue.


On Fri, Apr 9, 2010 at 11:11 AM, Michael Collins <msc at freeswitch.org> wrote:

>
>
> On Thu, Apr 8, 2010 at 9:38 PM, lakshmanan ganapathy <lakindia89 at gmail.com
> > wrote:
>
>> Right now I can't provide you the ssh access to the box, since the company
>> policy doesn't allow to do so.
>
>
> You might want to ask the company if they can lift that policy for the sake
> of saving everyone's time and energy. I know we have some professionals who
> would be willing to sign a reasonable NDA or whatnot to ensure security.
> -MC
>
>
>> But I can explain you more clearly about
>> the setup and my need.
>>
>> The following is the setup.
>> >From a Telephone Exchange, a line will be connected to the FS-BOX,  in
>> span1.
>> We have an internal Hard PBX with some 4 extensions.
>> We have connected the Hard PBX to FS-BOX in span2.
>>
>> I've configured span1 as PRI_CPE and span2 as PRI_NET.
>> span1 don't have any problems. Both incoming and outgoing works fine.
>> In span2, I was able to make incoming call. It rings the extension.
>> But when I make outgoing call from those extension, I got NO CIRCUIT OR
>> CHANNEL AVAILABLE.
>>
>> Right now in sangoma_mgd log, I got the following when I make outgoing
>> call.
>>
>> Apr  8 10:20:21 FMS-FreeSwitch sangoma_prid: Opening
>> /var/log/sangoma_pri/dchan_2.log
>> Apr  8 10:20:21 FMS-FreeSwitch sangoma_prid: Rx Tsoft [s2c0 7:StatusIn
>> 3:134716232 id:65535]
>> Apr  8 10:20:21 FMS-FreeSwitch sangoma_prid: Rx Tsoft [s2c0 7:StatusIn
>> 4:134716308 id:65535]
>>
>> Moreover I also have an Asterisk Box with Digim card. It works fine there.
>> When i dial from extension, it reaches asterisk and it responds with
>> SETUP_ACK.
>>
>> please guide me.
>>
>>
>> On Wed, Apr 7, 2010 at 10:44 PM, David Yat Sin <david.yatsin at gmail.com>
>> wrote:
>> >
>> > Can you provide me with SSH access to that box and a phone number I can
>> use to trigger an incoming call on span 2 to that box?
>> >
>> > You can email me at: dyatsin at sangoma.com
>> >
>> > David
>> >
>> > On 4/7/2010 4:48 AM, lakshmanan ganapathy wrote:
>> >
>> > Hi,
>> > I have set verbose=4 in smg_pri.conf.
>> > I started the wanrouter.
>> > Here is the sangoma_mgd.log
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: ================System
>> restart=============
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: = Sangoma PRI Protocol
>> Stack Daemon       =
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: = Version: 1.63
>>               =
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: = Date: Feb 26 2010
>>               =
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: = Wanpipe Release:
>> wanpipe-3.5.8.6       =
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: = Revision:Revision: 15607
>>                =
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid:
>> ===========================================
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: Number of spans:2
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: Verbosity set to:4
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: Log Debug disabled
>> (local:2)
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: Log Boost disabled
>> (local:6)
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: TSoft:span:1 pri_cpe
>> euroisdn dChan:16
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: TSoft:span:2 pri_net
>> euroisdn dChan:16
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: s2:Status:Up prot:Down
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: BST:(P) Local:
>> 127.0.0.66:53001 Remote:127.0.0.65:53001
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: BST:(N) Local:
>> 127.0.0.66:53000 Remote:127.0.0.65:53000
>> > Apr  7 13:58:25 FMS-FreeSwitch sangoma_prid: BST:Version:103
>> > Apr  7 13:58:27 FMS-FreeSwitch sangoma_prid: s2:Status:Up prot:Up
>> > Apr  7 13:58:31 FMS-FreeSwitch sangoma_prid: s1:Status:Up prot:Down
>> > Apr  7 13:58:32 FMS-FreeSwitch sangoma_prid: s1:Status:Up prot:Up
>> > Apr  7 13:58:37 FMS-FreeSwitch sangoma_prid: HeartBeat timeout
>> (current:13:58:37 last:13:58:26 grace:0)
>> > Apr  7 13:58:43 FMS-FreeSwitch sangoma_prid: Opening
>> /var/log/sangoma_pri/dchan_1.log
>> > Apr  7 13:58:47 FMS-FreeSwitch sangoma_prid: HeartBeat timeout
>> (current:13:58:47 last:13:58:37 grace:0)
>> > Apr  7 13:58:57 FMS-FreeSwitch sangoma_prid: HeartBeat timeout
>> (current:13:58:57 last:13:58:47 grace:0)
>> > Apr  7 13:58:57 FMS-FreeSwitch sangoma_prid: Assuming application is
>> dead
>> > Apr  7 13:59:07 FMS-FreeSwitch sangoma_prid: HeartBeat timeout
>> (current:13:59:07 last:13:58:57 grace:0)
>> > Apr  7 13:59:17 FMS-FreeSwitch sangoma_prid: HeartBeat timeout
>> (current:13:59:17 last:13:59:07 grace:0)
>> > Apr  7 13:59:27 FMS-FreeSwitch sangoma_prid: HeartBeat timeout
>> (current:13:59:27 last:13:59:17 grace:0)
>> > Apr  7 13:59:27 FMS-FreeSwitch sangoma_prid: Assuming application is
>> dead
>> > Apr  7 13:59:37 FMS-FreeSwitch sangoma_prid: HeartBeat timeout
>> (current:13:59:37 last:13:59:27 grace:0)
>> > Apr  7 13:59:47 FMS-FreeSwitch sangoma_prid: HeartBeat timeout
>> (current:13:59:47 last:13:59:37 grace:0)
>> > Apr  7 13:59:57 FMS-FreeSwitch sangoma_prid: HeartBeat timeout
>> (current:13:59:57 last:13:59:47 grace:0)
>> > Apr  7 13:59:57 FMS-FreeSwitch sangoma_prid: Assuming application is
>> dead
>> >
>> > >From freeswitch cli, if I say
>> > originate openzap/1/a/39114603 at g2 &park(), I got the following in the
>> sangoma_mgd.log.
>> >
>> > Apr  7 14:13:50 FMS-FreeSwitch sangoma_prid: g2:Outgoing call (Smg-ID:2)
>> > Apr  7 14:13:50 FMS-FreeSwitch sangoma_prid: s2:Outgoing call ChanRq:1
>> Called-Nb[39114603] Calling-Nb[Unknown] (Smg-ID:2)
>> > Apr  7 14:13:50 FMS-FreeSwitch sangoma_prid: s2c1:Remote
>> released-Unallocated (unassigned) number(1)
>> > Apr  7 14:13:50 FMS-FreeSwitch sangoma_prid: s2c0:Call was already
>> cleared (TSOFT-ID:4)
>> > Apr  7 14:13:50 FMS-FreeSwitch sangoma_prid: g2:Call cleared (SMG-ID:2)
>> >
>> > By seeing this, I confirmed that span2 is working. Leave out the
>> Unallocated number, that's my internal problem.
>> >
>> > >>From the extension, if I dial 0, nothing is printing in
>> sangoma_mgd.log
>> > But in dhcan2.log I got the No/Circuit or channel available as I
>> mentioned earlier.
>> >
>> > In freeswitch mod_openzap is loaded properly.
>> > Any help!!!
>> >
>> >
>> > On Wed, Apr 7, 2010 at 2:17 AM, David Yat Sin <david.yatsin at gmail.com>
>> wrote:
>> >>
>> >> Hi Lakshmanan,
>> >> If you do not have anything printing in /var/log/sangoma_mgd.log, and
>> you have:
>> >> verbose=4           //(or higher)
>> >>
>> >> in /etc/wanpipe/smg_pri.conf, check that you have these lines in
>> /etc/syslog.conf (or /etc/rsyslog.conf):
>> >>
>> >> local2.*                /var/log/sangoma_mgd.log
>> >>
>> >> and restart your syslog.
>> >>
>> >>
>> >> my first guess is that you do not have openzap loaded so sangoma_prid
>> is rejecting all incoming calls, but I would need logs in
>> /var/log/sangoma_mgd.log to confirm.
>> >>
>> >> If openzap is not loaded, you can type:
>> >> load mod_openzap
>> >>
>> >> from the freeswitch CLI to load it.
>> >>
>> >> --
>> >>
>> >> David Yat Sin, BEng, Software Developer
>> >> Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON
>> L3R 9T3 Canada
>> >> t. 1 905 474 1990 x 119 | e. dyatsin at sangoma.com
>> >>
>> >>
>> >>
>> >> On 4/6/2010 12:24 AM, lakshmanan ganapathy wrote:
>> >>
>> >> Hi all,
>> >> In my office we have a Hard PBX, with some 4 extensions.
>> >> We also have sangoma A102 card.
>> >> >From the Hard PBX, if 0 is pressed, it is setup in a way that it will
>> go to outside world.
>> >> I've connected that line to span2 of the card.
>> >> The span2 in the A102 card, is configured as PRI_NET.
>> >>
>> >> wanrouter status shows connected for the span2.
>> >>
>> >> But if I dial from the extension, I got the following in the
>> sangoma_dchan log.
>> >> 2010-04-03 12:49:49
>> >> INCOMING [ 00 01 54 50 08 02 01 64 05 04 03 80 90 a3 6c 0c 01 81 34 34
>> 33 39 31 31 34 36 30 30 7d 02 91 81 ]
>> >>   Call Ref:0164
>> >>   Type:Setup (0x5)
>> >>   Bearer Capability:Coding:ITU-T(0) TransferCap:Speech(0)
>> TransferRate:64 Kbit/s(16) L1Prot:G.711 A-Law(3)
>> >>   Calling Party Number:4439114600(l:10) plan:isdn(1)
>> type:unknown(0)scr:user, passed(1) pres:allowed(0)
>> >>   High-Layer Compatibility:Undecodedhex [ 7d 02 91 81 ]
>> >>
>> >> 2010-04-03 12:49:49
>> >> OUTGOING [ 02 01 50 56 08 02 81 64 5a 08 02 82 a2 ]
>> >>   Call Ref:0164
>> >>   Type:Release Compl (0x5a)
>> >>   Cause:coding:ITU-T(0) location:Public network, local user(2) val:No
>> Circuit/Channel Available(34)
>> >>
>> >> The call in not reaching freeswitch ( I enabled debug log. But nothing
>> is printing in it ).
>> >> Can someone suggest how to make this work.
>> >>
>> >> Please ask me if you need more information?, since I don't know what to
>> give now.
>>
>> >>
>> >>
>> >> _______________________________________________
>> >> FreeSWITCH-users mailing list
>> >> FreeSWITCH-users at 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 at 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 at 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 at 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 at 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 at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20100417/3329cd1d/attachment-0001.html

More information about the FreeSWITCH-users mailing list