There is limitation on how any open file handles (this includes sockets too) OS can support. If this limit is reached, you get above exception. If you are on ∗ nix OS, this can be easily increased.
Open /etc/security/limits.conf
I am on Ubuntu so for me I just execute following command from command line
sudo gedit /etc/security/limits.conf
and add following two lines
∗ soft nofile 3072
∗ hard nofile 3072
Save and Close the file. I don't know how to load these settings from command prompt but rebooting did the trick. To make sure these changes are done execute
ulimit -n
If you know how to do it on windows please add comment.
Thanks.
Thursday, January 7, 2010
Saturday, January 2, 2010
Mobicents JAIN SLEE Server 2.x unites in league of JOPR Console!
JBoss Operations Network (JOPR) is becoming the de-facto for managing suite of JBoss products and rightly so as it provides administration, monitoring, alerting, operational control and configuration in an enterprise setting with fine-grained security and an advanced extension model.
Since Mobicents Sip Servlets Server is already having JOPR agent and we have experienced how easy it becomes when it comes to management using JOPR JAIN SLEE server team also decided to venture on JOPR so all the products of Mobicents have same look and feel and can be managed from same Console.
Big thanks goes to JOPR team for answering all the queries that really saved lot of time had we tried to solve them by ourselves.
The features of Mobicents JSLEE (version 2.x.y) JOPR is in-line with Mobicents Management Console that is available with Mobicents JSLEE Server 1.x.y.
The JOPR Agent (binary) for Mobicents JSLEE will soon be available with release Mobicents JAIN SLEE Server version 2.0.0CR1. However if you are getting little impatient and want to give it a try right away, download the source code from mobicents svn and call 'mvn clean install'. You should see the agent jar at jopr-plugin/target/mobicents-slee-jopr-as-5-plugin-2.0.0-SNAPSHOT.jar
The Agent is built using the source RHQ 1.4.x trunk.
The first binary release of RHQ 1.4.0.b01 server can be downloaded from here. Follow the blog from Heiko to know more about this release.
Unzip rhq-server-1.4.0.B01.zip and start the server from 'rhq-server-1.4.0.B01/bin' using 'rhq-server.sh start'. Once server is started visit http://localhost:7080/. First time it will ask for configuring the Database and for test you can simply select the HSQLDB. To know more about installation of JOPR have a look at http://community.jboss.org/wiki/jopr-installation.
You also need to have JOPR Agent, I found one in rhq-server-1.4.0.B01/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-agent/rhq-enterprise-agent-1.4.0.B01.jar. Unjar it and start the Agent from 'rhq-enterprise-agent-1.4.0.B01/rhq-agent/bin' by executing 'rhq-agent.sh -l' (-l argument is only for first time to configure the agent, the subsequent starts can be done by executing command 'rhq-agent.sh'). It will ask few questions for configuring agent and has default answers for each, just press 'enter' for each.
To install the Mobicents JAIN SLEE JOPR Plugin using Jopr UI, go to Administration → System Configuration → Plugins. On the Agent Plugins tab (selected by default), on the bottom of the page, click on Add..., browse to the Jopr plugin JAR file and select it. Finally, click on the Upload button and the plugin will be deployed. Click on Scan for Updates and it should be shown in the list as "Mobicents JSLEE Server 2.x". On the Agent Console call 'Plugins Update'.
This will deploy the Plugin on Agent side and it will automatically discover your Mobicents JAIN SLEE Server 2.x.y. To add mobicents server to RHQ Server go to Overview → Auto Discovery Queue on server page and Import Mobicents JAIN SLEE Server. If you don't see an entry like 'Mobicents JAIN SLEE Server 2.x.y (:port) something went wrong and check necessary logs of server and agent.
Voilà! You have JOPR monitoring your Mobicents JAIN SLEE Server and it should look something like this
If you want to know more about how to manage JAIN SLEE Server, build the docs by calling 'mvn clean install' from /jopr-plugin/docs and browse the docs.
Enjoy the new shiny management console!
Please post queries to mobicents-public@googlegroups.com
Since Mobicents Sip Servlets Server is already having JOPR agent and we have experienced how easy it becomes when it comes to management using JOPR JAIN SLEE server team also decided to venture on JOPR so all the products of Mobicents have same look and feel and can be managed from same Console.
Big thanks goes to JOPR team for answering all the queries that really saved lot of time had we tried to solve them by ourselves.
The features of Mobicents JSLEE (version 2.x.y) JOPR is in-line with Mobicents Management Console that is available with Mobicents JSLEE Server 1.x.y.
The JOPR Agent (binary) for Mobicents JSLEE will soon be available with release Mobicents JAIN SLEE Server version 2.0.0CR1. However if you are getting little impatient and want to give it a try right away, download the source code from mobicents svn and call 'mvn clean install'. You should see the agent jar at jopr-plugin/target/mobicents-slee-jopr-as-5-plugin-2.0.0-SNAPSHOT.jar
The Agent is built using the source RHQ 1.4.x trunk.
The first binary release of RHQ 1.4.0.b01 server can be downloaded from here. Follow the blog from Heiko to know more about this release.
Unzip rhq-server-1.4.0.B01.zip and start the server from 'rhq-server-1.4.0.B01/bin' using 'rhq-server.sh start'. Once server is started visit http://localhost:7080/. First time it will ask for configuring the Database and for test you can simply select the HSQLDB. To know more about installation of JOPR have a look at http://community.jboss.org/wiki/jopr-installation.
You also need to have JOPR Agent, I found one in rhq-server-1.4.0.B01/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-agent/rhq-enterprise-agent-1.4.0.B01.jar. Unjar it and start the Agent from 'rhq-enterprise-agent-1.4.0.B01/rhq-agent/bin' by executing 'rhq-agent.sh -l' (-l argument is only for first time to configure the agent, the subsequent starts can be done by executing command 'rhq-agent.sh'). It will ask few questions for configuring agent and has default answers for each, just press 'enter' for each.
To install the Mobicents JAIN SLEE JOPR Plugin using Jopr UI, go to Administration → System Configuration → Plugins. On the Agent Plugins tab (selected by default), on the bottom of the page, click on Add..., browse to the Jopr plugin JAR file and select it. Finally, click on the Upload button and the plugin will be deployed. Click on Scan for Updates and it should be shown in the list as "Mobicents JSLEE Server 2.x". On the Agent Console call 'Plugins Update'.
This will deploy the Plugin on Agent side and it will automatically discover your Mobicents JAIN SLEE Server 2.x.y. To add mobicents server to RHQ Server go to Overview → Auto Discovery Queue on server page and Import Mobicents JAIN SLEE Server. If you don't see an entry like 'Mobicents JAIN SLEE Server 2.x.y (
Voilà! You have JOPR monitoring your Mobicents JAIN SLEE Server and it should look something like this
If you want to know more about how to manage JAIN SLEE Server, build the docs by calling 'mvn clean install' from /jopr-plugin/docs and browse the docs.
Enjoy the new shiny management console!
Please post queries to mobicents-public@googlegroups.com
Tuesday, December 22, 2009
IEEE paper on "Developing Converged Application using Open Source software"
The 2009 IEEE Symposium on Industrial Electronics & Applications was held at Best Western Premier Seri Pacific Hotel, Kuala Lumpur, Malaysia on 4th-6th October 2009. From RedHat/Mobicents I submitted paper on "Developing Converged Application using Open Source software" and presented the same on 5th October 2009. The paper is already registered in the IEEE Xplore database. The paper talks about leveraging the Open Source Solution in development of real time application like voice. The paper then talks in details about Mobicents Platform, components involved in Mobicents Platform and finally a converged example developed on Mobicents Platform.
Thursday, September 24, 2009
Encounter with JOPR
There is a discussion for Mobicents Media Server 2.x.y Console requirements on
In quest to understand what exactly is JOPR I decided to write a custom plugin for JOPR and see how it can monitor any resource's that we want.
I started with blog from Heiko and this was very useful. Thank you JOPR guys for such a niece blog! After reading all 5 Part's I decided to give it a try.
Started with SVN check-out of JOPR from http://svn.rhq-project.org/repos/rhq/trunk to my local directory /jopr/src/
Since JOPR is also using maven, building JOPR was not nightmare. However JOPR by default requires the access to Postgres database and it wasn't easy for me to install Postgres and get it running :( I wish JOPR uses in-memory HSQLDB initially and latter on give an option to go for Postgres, Oracle, My-Sql or any DB that user may want to use in production. This will make the development very fast.
The wiki explaining the build of JOPR is given at http://support.rhq-project.org/display/RHQ/Building+RHQ
Once you have JOPR built and installed and have Postgres up and running, you need to develop a custom plugin as explained in Part3 of blog.
Assuming that custom plugin is built and ready, next step is start the server
So far so good. The conclusion is Agent needs to be installed on Mobicents Media Server that we need to monitor and Agent communicate to server Via JBoss Remoting. I am still learning what is the communication protocol and what is the load on client machine where Agent is installed due to agent activity. Remember Mobicents Media Server cannot take any heavy load else Jitter will kill all the performance.
Its now clear that we can expose the statistics using JOPR. Next I want to write a Agent that talks to MMS via MGCP protocol to avoid installing Agent at MMS side and expose some real statistics. Also one of the requirements of MMS Console is configuring the media-path at run-time with easy drag-and-drop feature from console. I still don't know if this is possible via JOPR Agent? And if yes can it be remote or needs to be in same JVM as Mobicents Media Server?
May be I will ask the JOPR experts to help me out with this dilemma.
Till then enjoy the JOPR :)
- whether it should be built using Swing that can be installed on any machine and this stand-alone instance connects with Mobicents Media Server for statistics and configuration
OR
- use standard JOPR server that almost all Mobicents project is using as de-facto and write agent that will monitor media server.
In quest to understand what exactly is JOPR I decided to write a custom plugin for JOPR and see how it can monitor any resource's that we want.
I started with blog from Heiko and this was very useful. Thank you JOPR guys for such a niece blog! After reading all 5 Part's I decided to give it a try.
Started with SVN check-out of JOPR from http://svn.rhq-project.org/repos/rhq/trunk to my local directory /jopr/src/
Since JOPR is also using maven, building JOPR was not nightmare. However JOPR by default requires the access to Postgres database and it wasn't easy for me to install Postgres and get it running :( I wish JOPR uses in-memory HSQLDB initially and latter on give an option to go for Postgres, Oracle, My-Sql or any DB that user may want to use in production. This will make the development very fast.
The wiki explaining the build of JOPR is given at http://support.rhq-project.org/display/RHQ/Building+RHQ
Once you have JOPR built and installed and have Postgres up and running, you need to develop a custom plugin as explained in Part3 of blog.
Assuming that custom plugin is built and ready, next step is start the server
- cd to /jopr/src/trunk/modules/enterprise/server/container/target/rhq-server-1.3.0-SNAPSHOT/bin and call ./rhq-server.sh start
- Go to http://localhost:7080/ to see the JOPR console. Login as user rhqadmin and password rhqadmin
- Still we haven't started the Agent. So next cd to /jopr/src/trunk/modules/enterprise/agent/target/rhq-agent/bin and ./rhq-agent.sh -l. This will configure the Agent and ask few simple questions. For almost all of them the default answers are rigtht. Bellow is from my comandline showing what reply I provided
RHQ 1.3.0-SNAPSHOT [4925] (Thu Aug 20 13:44:46 GMT+05:30 2009)
Answer the following questions to setup this RHQ Agent instance.
- After each prompt, a default value will appear in square brackets.
If you press the ENTER key without providing any value,
the new preference value will be set to that default value.
- If you wish to rely on the system internal default value and
not define any preference value, enter '!*'.
- If you wish to stop before finishing all the questions but still
retain those preferences you already set, enter '!+'.
- If you wish to cancel before finishing all the questions and revert
all preferences back to their original values, enter '!-'.
- If you need help for a particular preference, enter '!?'.
Agent Name [localhost] : postgres_agent
Agent Hostname or IP Address [!*] :
Agent Port [16163] :
RHQ Server Hostname or IP Address [127.0.0.1] :
RHQ Server Port [7080] :
The setup has been completed for the preferences at node [/rhq-agent/default].
Next from client CLI I executed command 'plugins' just to refresh the plugins from server. - Now go to http://localhost:7080/ Click on Dashboard - Auto-Discovery and you should see entry of the 'postgres_agent' agent. Import this Agent and now all the statistics including the custom plugin that we developed will be available to JOPR Server and we can monitor the stats. Below is the Screen shot showing the Response Time metrics exposed by our custom plugin.
So far so good. The conclusion is Agent needs to be installed on Mobicents Media Server that we need to monitor and Agent communicate to server Via JBoss Remoting. I am still learning what is the communication protocol and what is the load on client machine where Agent is installed due to agent activity. Remember Mobicents Media Server cannot take any heavy load else Jitter will kill all the performance.
Its now clear that we can expose the statistics using JOPR. Next I want to write a Agent that talks to MMS via MGCP protocol to avoid installing Agent at MMS side and expose some real statistics. Also one of the requirements of MMS Console is configuring the media-path at run-time with easy drag-and-drop feature from console. I still don't know if this is possible via JOPR Agent? And if yes can it be remote or needs to be in same JVM as Mobicents Media Server?
May be I will ask the JOPR experts to help me out with this dilemma.
Till then enjoy the JOPR :)
Friday, September 4, 2009
Mobicents Annual Meet at Brno Czech Republic - August 24 - 29, 2009
Last week Mobicents core team met at Brno, Czech Republic to discuss the achievements and road-map of Mobicents platform. Some brain storming between all the projects and some learning and party at the end of the day is something that is equally important :)
This time too it was as exciting as last year. This was third time Mobicents core team met, and each one of us did presentations of the project we are working on. The agenda of the meet was:
The major achievements of the past year is Mobicents Media Server, Mobicents Sip Servlet Server, Mobicents JAIN SLEE Server and Mobicents Diameter all went GA! Mobicents JAIN SLEE Server is already JAIN SLEE 1.1 compliant.
This couldn't have been possible without the continuous support of the community. For all the discussions, presentation and blogs from other team members please visit Mobicents Brno page.
I did two presentations on MMS 2.x.y architecture and role of MMS in SS7 world.
MMS 2.x.y architecture makes it one of the most flexible and the only OpenSource media server available as of today built on top of JBoss Microcontainer.
For SS7 support, Zaptel compatible SS7 cards will be installed on MMS and MMS core will take care of media circuit. For signaling the lower level parsing of MTP2 and MTP3 will be done by MMS and then depending on the protocol the message will be forwarded to corresponding stack wrapped by JAIN SLEE resource adaptor for handling the signaling and business logic in SBBs. Going forward we will have complete SS7 support like ISUP, SCCP, TCAP, MAP, etc. This will bridge the gap between legacy and next generation applications.
We marked day end by team dinner at some real good restaurant's and visiting pub's. Also enjoyed playing soccer at Public Garden and Go-Karting on one of the evenings.
The Team from Left to Right : Jean, Ivelin, Amit, Luis, Bartek, Vladimir, Alex and Eduardo. Our host Pavel is missing.
RedHat, Brno office has great infrastructure and they also have Wii Game Console. Bartek killed me 'n' number of times while playing 'James Bond: Quantum of Solace'. "I will get back with vengeance Bartek"
The beer of Brno is worth mentioning, they have different varieties of beer and we didn't leave a single chance to savour it ;)
From left to right Vladimir, Alex and Eduardo
Thats me and Vladimir
Extreme right is Pavel. A big thanks to Pavel for arranging everything :) The team walking on a mission after beer.
The mystery man Oleg couldn't make this time either :( I hope one day will come when GOD's are happy and we will get blessing to meet Oleg face-to-face. Other members missing from team are Vicky and Jared.
This time too it was as exciting as last year. This was third time Mobicents core team met, and each one of us did presentations of the project we are working on. The agenda of the meet was:
- Overview of project status, partner ecosystem and market opportunities; internal training for pre-sales and consulting teams.
- Productization achievements in 2009 and current challenges. Comparison with JBoss EAP and SOA productization. Goals and milestones for 2009-2010.
- Documentation, achievements in 2009. Current process, challenges and goals
- QE: achievements in 2009, current QE lab setup, automated test harness, outstanding challenges, what to expect in 2009-2010
- MSS achievements, challenges and roadmap
- IPBX Demo, STF, Ruby API
- MMS achievements, challenges and roadmap, what to expect in 2009-2010
- Diameter achievements, challenges and roadmap, what to expect in 2009-2010
- Mobicents JSLEE 2.x.y achievements, challenges and roadmap, what to expect in 2009-2010
- Presence Services achievements, challenges and roadmap, what to expect in 2009-2010
- 3G and IMS
- MMS - SS7 review, use cases, implementation strategies
- HA status, implementation roadmap alternatives, cross-server strategy
The major achievements of the past year is Mobicents Media Server, Mobicents Sip Servlet Server, Mobicents JAIN SLEE Server and Mobicents Diameter all went GA! Mobicents JAIN SLEE Server is already JAIN SLEE 1.1 compliant.
This couldn't have been possible without the continuous support of the community. For all the discussions, presentation and blogs from other team members please visit Mobicents Brno page.
I did two presentations on MMS 2.x.y architecture and role of MMS in SS7 world.
MMS 2.x.y architecture makes it one of the most flexible and the only OpenSource media server available as of today built on top of JBoss Microcontainer.
For SS7 support, Zaptel compatible SS7 cards will be installed on MMS and MMS core will take care of media circuit. For signaling the lower level parsing of MTP2 and MTP3 will be done by MMS and then depending on the protocol the message will be forwarded to corresponding stack wrapped by JAIN SLEE resource adaptor for handling the signaling and business logic in SBBs. Going forward we will have complete SS7 support like ISUP, SCCP, TCAP, MAP, etc. This will bridge the gap between legacy and next generation applications.
We marked day end by team dinner at some real good restaurant's and visiting pub's. Also enjoyed playing soccer at Public Garden and Go-Karting on one of the evenings.
The Team from Left to Right : Jean, Ivelin, Amit, Luis, Bartek, Vladimir, Alex and Eduardo. Our host Pavel is missing.RedHat, Brno office has great infrastructure and they also have Wii Game Console. Bartek killed me 'n' number of times while playing 'James Bond: Quantum of Solace'. "I will get back with vengeance Bartek"
The beer of Brno is worth mentioning, they have different varieties of beer and we didn't leave a single chance to savour it ;)
From left to right Vladimir, Alex and Eduardo
Thats me and Vladimir
Extreme right is Pavel. A big thanks to Pavel for arranging everything :) The team walking on a mission after beer.The mystery man Oleg couldn't make this time either :( I hope one day will come when GOD's are happy and we will get blessing to meet Oleg face-to-face. Other members missing from team are Vicky and Jared.
Sunday, August 16, 2009
JBoss World 2009 - Chicago September 1-4, 2009
Its time of year when JBoss World 2009 event will rock the stage! This time JBoss World and RedHat summit are hosted together. From Mobicents perspective, there are two sessions happening
First is "Rapid VoIP development - SIP Servlets 1.1, Seam Telco Framework, JRuby on Rails, Eclipse VoIP tooling" that will talk about the framework/tools developed by Mobicents that can facilitate the faster and better development of Converged Application. This seminar will be very productive for developers who wants to dive in VoIP world and also for vetrans who already knows the details.
Next is "Writing Telco 2.0 applications with JBoss Communications Platform based on Mobicents" which will focus on all available pieces of JBoss Communications Platform like JBCP JSLEE Server, JBCP Sip Servlets Server, JBCP Media Server, JBCP Presence Server, JBCP Diameter Server. For a Business decision makers who are planing to embark on "Converged Application" business, this could give a very good overview of what all pieces you need to make a comprehensive converged application. This will also be good for developers as it will give over all picture of JBCP components and how they fit with each other.
If you haven't yet registered, now is the time!
For people who attended the Mobicents presentation last year will be amazed by how much we progressed in just 1.5 years!
Enjoy the sessions and do let us know your feedback.
Cheers
First is "Rapid VoIP development - SIP Servlets 1.1, Seam Telco Framework, JRuby on Rails, Eclipse VoIP tooling" that will talk about the framework/tools developed by Mobicents that can facilitate the faster and better development of Converged Application. This seminar will be very productive for developers who wants to dive in VoIP world and also for vetrans who already knows the details.
Next is "Writing Telco 2.0 applications with JBoss Communications Platform based on Mobicents" which will focus on all available pieces of JBoss Communications Platform like JBCP JSLEE Server, JBCP Sip Servlets Server, JBCP Media Server, JBCP Presence Server, JBCP Diameter Server. For a Business decision makers who are planing to embark on "Converged Application" business, this could give a very good overview of what all pieces you need to make a comprehensive converged application. This will also be good for developers as it will give over all picture of JBCP components and how they fit with each other.
If you haven't yet registered, now is the time!
For people who attended the Mobicents presentation last year will be amazed by how much we progressed in just 1.5 years!
Enjoy the sessions and do let us know your feedback.
Cheers
Tuesday, April 28, 2009
Sangoma & Asterisk + SS7
This is in continuation to my earlier blog on Asterisk + SS7
Here I will jot down my experience on installing wanpipe drivers for new Sangoma A102 card. I bought this card for approximately 60000 INR which is approximately 1350 USD. Just FYI, if any of you guys planing to buy, not sure if its expensive?. I started with downloading Wanpipe drivers and downloaded the most recent 3.3.16 Beta version from http://wiki.sangoma.com/wanpipe-linux-drivers#beta.
Untar this to /usr/src directory
From /usr/src/wanpipe call 'sudo ./Setup dahdi' This will ask you few questions like where is your dahdi installation (point to directory of dahdi). If you have installed dahdi at default location it will automatically give you an option to select that. You will find info at wiki http://wiki.sangoma.com/wanpipe-linux-asterisk-dahdi. I really was looking for way to update this wiki with all the questions that I faced while installing and answers I provided, but unfortunately I didn't find a way to edit the wiki. Though there is an option to leave comment but didn't like that :( Sangoma people can you please make this more dynamic?
Once the compilation of drivers is successful, the Setup will ask you to configure the Channels. This is interesting part and one that kept failing at my end with error message
"No Sangoma voice compatible cards found/configured"
I was having hardware and could see the lights glowing so definitely there was no problem with hardware or PCI slot. I tried executing the command 'sudo wanrouter hwprobe' and would always get
wanrouter: Wanpipe Module: /lib/modules/2.6.24-23-generic/kernel/drivers/net/wan/sdladrv not found !!!!
WANPIPE drivers must be compiled as modules
Check kernel configuration in /usr/src/linux/.config:
CONFIG_WAN_ROUTER=m
CONFIG_VENDOR_SANGOMA=m
I had to ping Sangoma support for this. You can find contact details for support at http://wiki.sangoma.com/SangomaTechSupport
Marc from Sangoma was really quick on this one to help me out. Thanks you Marc Celsie! As per support I had to edit /lib/modules/2.6.24-23-generic/build/Makefile and remove line "EXTRAVERSION = .6". Then change "SUBLEVEL = 24" to "SUBLEVEL = 24-23-generic". After this I had to re-execute the command 'sudo ./Setup dahdi' and it worked like a charm. I set-up the E1 lines and could see 62 channels getting created at /dev/dahdi/1 ... /dev/dahdi/62. The LED at both the port (A-102 has two ports) is now Red which means the drivers installation is good but there is no traffic.
I created a loop-back as shown in this image http://www.t1installers.com/wp-includes/images/loopback/clip_image002.jpg
Pin-outs for the loopback cable:
1<->4
2<->5
And inserted in one of the ports and LED turns Green!
Execute 'ifconfig' command number of times and you will see the tx and rx value increasing for port where you have loopback wire plugged. This is proof that everything is good so far.
After this comes the configuration files for Asterisk to talk to your hardware. I am doing this as of now and will post soon in my next blog.
Stay Tunned!
Here I will jot down my experience on installing wanpipe drivers for new Sangoma A102 card. I bought this card for approximately 60000 INR which is approximately 1350 USD. Just FYI, if any of you guys planing to buy, not sure if its expensive?. I started with downloading Wanpipe drivers and downloaded the most recent 3.3.16 Beta version from http://wiki.sangoma.com/wanpipe-linux-drivers#beta.
Untar this to /usr/src directory
From /usr/src/wanpipe call 'sudo ./Setup dahdi' This will ask you few questions like where is your dahdi installation (point to directory of dahdi). If you have installed dahdi at default location it will automatically give you an option to select that. You will find info at wiki http://wiki.sangoma.com/wanpipe-linux-asterisk-dahdi. I really was looking for way to update this wiki with all the questions that I faced while installing and answers I provided, but unfortunately I didn't find a way to edit the wiki. Though there is an option to leave comment but didn't like that :( Sangoma people can you please make this more dynamic?
Once the compilation of drivers is successful, the Setup will ask you to configure the Channels. This is interesting part and one that kept failing at my end with error message
"No Sangoma voice compatible cards found/configured"
I was having hardware and could see the lights glowing so definitely there was no problem with hardware or PCI slot. I tried executing the command 'sudo wanrouter hwprobe' and would always get
wanrouter: Wanpipe Module: /lib/modules/2.6.24-23-generic/kernel/drivers/net/wan/sdladrv not found !!!!
WANPIPE drivers must be compiled as modules
Check kernel configuration in /usr/src/linux/.config:
CONFIG_WAN_ROUTER=m
CONFIG_VENDOR_SANGOMA=m
I had to ping Sangoma support for this. You can find contact details for support at http://wiki.sangoma.com/SangomaTechSupport
Marc from Sangoma was really quick on this one to help me out. Thanks you Marc Celsie! As per support I had to edit /lib/modules/2.6.24-23-generic/build/Makefile and remove line "EXTRAVERSION = .6". Then change "SUBLEVEL = 24" to "SUBLEVEL = 24-23-generic". After this I had to re-execute the command 'sudo ./Setup dahdi' and it worked like a charm. I set-up the E1 lines and could see 62 channels getting created at /dev/dahdi/1 ... /dev/dahdi/62. The LED at both the port (A-102 has two ports) is now Red which means the drivers installation is good but there is no traffic.
I created a loop-back as shown in this image http://www.t1installers.com/wp-includes/images/loopback/clip_image002.jpg
Pin-outs for the loopback cable:
1<->4
2<->5
And inserted in one of the ports and LED turns Green!
Execute 'ifconfig' command number of times and you will see the tx and rx value increasing for port where you have loopback wire plugged. This is proof that everything is good so far.
After this comes the configuration files for Asterisk to talk to your hardware. I am doing this as of now and will post soon in my next blog.
Stay Tunned!
Subscribe to:
Posts (Atom)
