jeanpoman
asked on
Old PC to run Open H323 Gatekeeper. How to configure it and where to get it
Dr-IP provided me with this solution to my problem to terminate voip calls to a voip partner; Can he or anyone else tell me what would be the dial-peer config on both cases and how to implemente the last option of Openh323 ?
Here is Dr-IP comments on one of my previous questions:
" You can also use a crossover cable between the E1 ports to do effectively the same thing, but that ties up two E1 ports on the gateway which isn’t an optimal solution most of the time. Another solution would be to get an old PC and run OpenH323 Gatekeeper on it which is free, and would give you more flexibility, especially if you continue to expand your network with additional gateways "
Please help
Here is Dr-IP comments on one of my previous questions:
" You can also use a crossover cable between the E1 ports to do effectively the same thing, but that ties up two E1 ports on the gateway which isn’t an optimal solution most of the time. Another solution would be to get an old PC and run OpenH323 Gatekeeper on it which is free, and would give you more flexibility, especially if you continue to expand your network with additional gateways "
Please help
Few things needed if you need more specifics than the link above may provide:
1. Your current configuration of gateway(s) both Cisco and non cisco
2. Will you be using this on a Windows system or Linux? I would go towards the Linux for a few two main reasons: stability and more available tools to work with.
Kindest regards
1. Your current configuration of gateway(s) both Cisco and non cisco
2. Will you be using this on a Windows system or Linux? I would go towards the Linux for a few two main reasons: stability and more available tools to work with.
Kindest regards
Jeanpo,
How are things coming along? Do you neda ny additional infomration?
Kindest regards
How are things coming along? Do you neda ny additional infomration?
Kindest regards
ASKER
if you use a crossover cable betwween E1 on you gateway .the call id for the call will be same as a result the gateway will know that the call is looped and the GW will drop the call.
I know OpenH323 Gatekeeper it works but not as good as a proper vendor gatekeeper although you could use it do not expect high quality call termination
I know OpenH323 Gatekeeper it works but not as good as a proper vendor gatekeeper although you could use it do not expect high quality call termination
I will double check to see if there is a way to turn off the logical loop of the Cisco Gateway, never knew that exsisted, learned something new today, its a good day indeed.
Would it be possible to add a rule to the outbound of the E1 loop to insert digits, so this way when recieved by the inbound loop it does not appear to be the same? Then you could remove the digits when recieved?
In regards to OH323 , how many calls per hour are you trying to terminate? Also how many calls per hour do you process thru your entire system?
Would it be possible to add a rule to the outbound of the E1 loop to insert digits, so this way when recieved by the inbound loop it does not appear to be the same? Then you could remove the digits when recieved?
In regards to OH323 , how many calls per hour are you trying to terminate? Also how many calls per hour do you process thru your entire system?
ASKER
I am trying to terminate 600 calls a day. This matter is turning my head and I am about to adandon the project.
Were you able to configure the OH323? I think by your previos response that you were having problems with the quality of it? 600 calls is really not alot and the system should be able to handle it. What has actually been happening with the calls? Have you been able to route the calls from call shop to voip partner? If this was solved, then it might just require a bit of tweaking to get you to handle your call volume.
Kindest regards
Kindest regards
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Jeanpoman,
DrIP provided the detailed version of my post above, I think with the current call volume, using the E1 loop with add/delete would be a good way to go. Once you have this implemented I would seriously look at moving to SIP. The open Sip Express Router can handle Thousands of calls per hour and SIP enables a much more flexable enviroment.
Kindest regards
DrIP provided the detailed version of my post above, I think with the current call volume, using the E1 loop with add/delete would be a good way to go. Once you have this implemented I would seriously look at moving to SIP. The open Sip Express Router can handle Thousands of calls per hour and SIP enables a much more flexable enviroment.
Kindest regards
One thing I should note, most switches by default if you send a call to them on the same E1 that it normally terminates it on, will send it back out on that same E1. Normally that is considered an undesirable trait because it causes loops, but in your case it could work for you. So maybe you should try sending the call to the switch using a prefix that is striped by the pots dial peer and see of the switch sends it back out.
" I would seriously look at moving to SIP. The open Sip Express Router can handle Thousands of calls per hour and SIP enables a much more flexable enviroment."
I have played both sides of the fence, and more when it comes to VOIP. I use H233, SIP, and MGCP protocols for VOIP networking, so you can say I am pretty open minded when it comes to VOIP protocols, but I a far from believing SIP is the cure all many have portrayed it to be. I have been listening for 5 years how SIP was going to revolutionaries VOIP, and was an early adopter, but haven’t seen it come even close to its promise.
After over 3 years H323 still accounts for more than 80% of my VOIP traffic, and even MGCP accounts for more traffic than SIP. The way I see it, the noise about SIP is unwarranted since the only place SIP seems to be going anywhere is for little SIP phones, while the big boys continue to run their VOIP networks on H323.
I have played both sides of the fence, and more when it comes to VOIP. I use H233, SIP, and MGCP protocols for VOIP networking, so you can say I am pretty open minded when it comes to VOIP protocols, but I a far from believing SIP is the cure all many have portrayed it to be. I have been listening for 5 years how SIP was going to revolutionaries VOIP, and was an early adopter, but haven’t seen it come even close to its promise.
After over 3 years H323 still accounts for more than 80% of my VOIP traffic, and even MGCP accounts for more traffic than SIP. The way I see it, the noise about SIP is unwarranted since the only place SIP seems to be going anywhere is for little SIP phones, while the big boys continue to run their VOIP networks on H323.
Dr-IP,
You have beed drinking Cisco Kool-aid to long (LOL). Actually glad to have some one in the VoIP area whose knowledge goes beyond the wiki at http://www.voip-info.org (pop shot at number VoIPs :) )
I will have to respectivley diasagree on the SIP (not saying it is the end all, but has the best change for winning the VoIP war). I have to head to a clients , but will add more later to this post and my reasoning.
I would like to see if you could answer why H.323 took hold in the past 3 years? (I have been listening to VoIP/CTI for 15 years) and have the answer why it did (at least my humble opionion).
Look forward to future posts with you Dr-IP
Kindest regards
Joel_Sisko
You have beed drinking Cisco Kool-aid to long (LOL). Actually glad to have some one in the VoIP area whose knowledge goes beyond the wiki at http://www.voip-info.org (pop shot at number VoIPs :) )
I will have to respectivley diasagree on the SIP (not saying it is the end all, but has the best change for winning the VoIP war). I have to head to a clients , but will add more later to this post and my reasoning.
I would like to see if you could answer why H.323 took hold in the past 3 years? (I have been listening to VoIP/CTI for 15 years) and have the answer why it did (at least my humble opionion).
Look forward to future posts with you Dr-IP
Kindest regards
Joel_Sisko
http://www.gnugk.org/gnugk-cisco-as5300.html