PRI line Integrtation with kazoo

[Himanshu]

Hello,

I have PBX box and have 1 PRI card (Astrisk TE110P Wildcard single span PCI card), I want to integrate PRI card with Kazoo and i am not able to do it properly. Can anyone provide me proper steps to integrate PRI card with Kazoo.

With the help of this link (https://2600hz.atlassian.net/wiki/display/Dedicated/Connecting+via+TDM) I think it will be possible once PRI card is detected in CENTOS it should work with Kazoo, now I have main concern how can I be able to make CentOS to detect my PRI card. 

[Himanshu Sharma]

Hello,

I have PBX box and have 1 PRI card (Astrisk TE110P Wildcard single span PCI card), I want to integrate PRI card with Kazoo and i am not able to do it properly. Can anyone provide me proper steps to integrate PRI card with Kazoo.

With the help of this link (https://2600hz.atlassian.net/wiki/display/Dedicated/Connecting+via+TDM) I think it will be possible once PRI card is detected in CENTOS it should work with Kazoo, now I have main concern how can I be able to make CentOS to detect my PRI card.

Thank You,
Himanshu Sharma

[Himanshu Sharma]

Hello All,

I have successfully installed and configured Dahdi driver and its working fine. I have execute the below command to check whether it is working or not.

dahdi_hardware

Getting this result:

pci:0000:05:01.0     wcte11xp+    e159:0001 Digium Wildcard TE110P T1/E1 Board

Now my concern is to enable FreeTDM module in FreeSWITCH, as I have read that 2600hz team has worked on that but its not enabled. Is there any option to enable this module or I need to build the source of FreeSWITCH with FreeTDM.

Thanks,

Himanshu Sharma

[Kirill Sysoev]

Hi Himanshu,

It seems this question appears from time to time through years over here..

The answer usually is:

- don't put all eggs into one basket;
- Kazoo is a SIP thing;
- create separate SIP/TDM gateway with your card and configure Kazoo to use it..

Regards,
Kirill

--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Darren Schreiber]

Actually Kazoo works great with FreeTDM. Let me dig up the instructions…

[Himanshu Sharma]

Hi Darren,

Thanks for your help. Have you got any instructions for me? I am waiting for your response.

Thanks,

Himanshu Sharma

On Monday, May 9, 2016 at 5:21:01 PM UTC+5:30, Himanshu wrote:

[Gaurav Sainni]

Hello Darren,

I was also looking to integrating PRI with Kazoo, Did you find any instruction on it ?

Actually, I was thinking to build Freeswitch from source with FreeTDM in it. Although, still not much documentation I am able to get online. 

Small guide or documentation will be really helpful and after successfully installation we would love to contribute it back to Kazoo wiki. So, its easily accessible to everyone.  

Thanks

Gaurav

[Darren Schreiber]

Hi there,

                Yes, you should build FreeSWITCH from source w/ FreeTDM. I’d actually recommend just skipping to 4.0 so that all our patches are in the core FreeSWITCH build, too.

 

                Once you’ve done that, there is some custom JSON to configure on the offnet/ documents to use the freetdm/ interface instead of the SIP interface. That is what I’m trying to dig up. But you can start by just installing 4.0 as that’s what you’re going to need for this to work in a useful way.

 

- Darren

[Vinay Saini]

Hello Darren,

I am working with Gaurav for the PRI integration. I am able to build and run freeswitch with mod_freetdm. Also If I run 'ftdm list' on fs_cli getting response like this:

ftdm list

+OK
span: 1 (PRI_1)
type: isdn
physical_status: ok
signaling_status: DOWN
chan_count: 31
dialplan: XML
context: public
dial_regex: 
fail_dial_regex: 
hold_music: 
analog_options: none

But now the problem is with connection between ecallmgr and freeswitch. Every time I make call with the registered device getting  403 Forbidden error like this:

2016-05-16 21:17:09.337577 [DEBUG] sofia.c:9168 1 acls to check for proxy
2016-05-16 21:17:09.337577 [DEBUG] sofia.c:9173 checking 192.168.1.130 against acl authoritative
2016-05-16 21:17:09.337577 [DEBUG] sofia.c:9213 IP 192.168.1.130 Rejected by acl "authoritative". Falling back to Digest auth.
2016-05-16 21:17:09.337577 [WARNING] sofia_reg.c:2852 Can't find user [te...@test.smartpbx.com] from 192.168.1.130
You must define a domain called 'test.smartpbx.com' in your directory and add a user with the id="test2" attribute
and you must configure your device to use the proper domain in it's authentication credentials.
2016-05-16 21:17:09.337577 [WARNING] sofia_reg.c:1703 SIP auth failure (INVITE) on sofia profile 'sipinterface_1' for [+91XXXX...@test.smartpbx.com] from ip 192.168.1.130

 

When I run "erlang nodes list" on cli getting following result:

USAGE:

--------------------------------------------------------------------------------

erlang listeners

erlang sessions <node_name>

erlang bindings

erlang handlers

erlang debug <on|off>

--------------------------------------------------------------------------------

Am I missing something? Please let me know how to solve this issue. 

Thanks

Vinay

[Darren Schreiber]

In your offnet doc, try something like this in the gateways section:

[

   {

       "prefix": "1",

       "codecs": [

           "PCMU",

           "PCMA"

       ],

       "endpoint_type": "freetdm",

       "span": "1",

       "channel_selection": "1",

       "progress_timeout": "9",

       "invite_format": "1npan",

       "server": "1.1.1.1",

       "username": "pri",

       "password": "pri",

       "realm": "2.2.2.2",

       "suffix": "",

       "format_from_uri": false

   }

]

should work. Note the "freetdm" endpoint type above.