similar to: Registering Asterisk to Lucent's MVAM Gatekeeper

All, I'm running (attempting to) ooh323 with Asterisk and a Cisco 2621XM router operating as a H.323 GateKeeper, however when I bring the Asterisk box up it registers successfully with the GateKeeper (exchanges GRQ/GCF, then RRQ/RCF) it notes the GateKeeper supports keepalive at 300 seconds, when it gets to time to re-register its sends an RRQ again and gets rejected with RRJ (unspecified

All, I've fixed my problem getting Asterisk ooh323 channel to stay registered with my Cisco IOPS gatekeeper, now I need to get dialling working. I have the following: [Asterisk with ooh323] ----h323---- [Cisco IOS GK] ----h323---- [Radio system OpenH323] 192.168.1.5 192.168.1.6 192.168.1.7 the Asterisk box has numbers

Has anyone had any luck getting Asterisk 1.6.2.13 to register to a Tandberg Gatekeeper? The logs on the Asterisk end seem to show that the registration request is sent, and the Tandberg Gatekeeper responds. However, the response doesn't seem to be what Asterisk was expecting. Here is my ooh323.conf, followed by the relevant portion of the h323_log: [general] port = 1720 bindaddr =

Hi there, I would like to communicate H323 IP phones with SIP phones. My H323 phones are registered to a gnugk GK, and the SIP phones are registered to a asterisk SIP proxy. I could not create a dialplan that works. Inside my extensions.conf file I created the following two entrances: exten => 4,1,Dial(SIP/4) exten => 5,1,Dial(SIP/5) This allows SIP phones call each other.

Hi, I am using a cisco 7912. I setup the phone at my first location. I edited the gk<MAC>.txt file setup the proxy and UID etc... values. generated the gk<MAC> file and booted the phone and it worked... I then mailed it to its final destination. this place has other 7912 phones working there.. I copied the gk<MAC>.txt file to that server, changed the proxy and UID values,

Hi, I'm trying to configure Asterisk as SIP-H.323 Gateway via ooh323, but I have an error relatively to the GK Confirmation message. >From the log: "H323 RAS channel creation - succesful Sent GRQ message Gatekeeper Confirmed (GCF) message received ERROR:No Gatekeeper ID present in received GKconfirmed message Ignoring message and will retransmit GRQ after timeout Error: Failed to

Dear Mailinglist-User currently we`re working with an IP-PBX, based on Asterisk, with SIP, H.323 and ISDN-Capabilities. SIP and ISDN works fine, but H.323 not. In our first test, we started to connect Asterisk to an Cisco IOS-Gatekeeper with the "chan_oh323" (version 0.6.5). We successfully tested in/egress calls without any problems. But when we started to connect our Asterisk

I'm trying to connect an Asterisk 1.6 to an Avaya with gatekeeper (CLAN). When chan_ooh323 first loads it tries to establish a connection with the gk but I it fails. I have the following extract from the ooh323 log. Can anyone give some insight? Thanks! MD 23:02:59:045 Sent GRQ message 23:02:59:045 GkClient Received RAS Message 23:02:59:045 Received RAS Message = { 23:02:59:045

Hi there, I know this question is kind of stupid. But, I don't know anywhere else to ask. I've received some answers when I asked about the need of having a zaptel interface to make the meetme application work, that said that it was better to have a real hardware then the zaptelrtc software modules. So, my question is, would any of the following cards work with the meetme

Hello, I'm trying to register with a gatekeeper using chan_h323, I have a Login, Password and a user (telephone) number, This is my h323.conf [general] port=1720 bindaddr=x.x.x.x (my fixed IP) gatekeeper=x.x.x.x (gk ip) allowgkrouted=yes allow=all [xx] (my login) type=h323 e164=111 (my assigned phone number) secret=1111 (my password) context=incoming I'm getting this error when trying

Hi there, Here at my company we are willing to use the asterisk IVR system. The problem we are having rigth now is that all our GWs use G729. I've read that in order to asterisk be able to make transcoding from the GSM audio files to G.729, it is necesary to purchase a license from digium. Is this correct? I've seen that licenses are purchased on a per-channel basis. Could

Hello every one, I have got a H323 gatekeeper for testing. The informations are something like this: account code: test01 gk ip address:192.168.10.12 I don't know how to set it in the h323.conf or oh323.conf, I have tried it for almost one day but I always got the error. Help me please. Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL:

All, I'm haveing a bit of trouble getting my head around H.323 and call routing with Gatekeepers, Zones and intra-zone calls - hopefully someone who is more informed in things H.323 will be able to point me in the right direction...? I already have a mature network of Asterisk boxes dotted around the UK and overseas with hundreds of extensions and our own number-plan/dial-plan in the form

Hi there, I have the following scenario: I have a GK that controls my H323 GWs. And, I am needing an IVR royalty-free system. More than an IVR, it's only something that should play a sound file depending on the called digits. So, I wanted to use asterisk as my IVR. So, I've installed asterisk with the chan_h323 module and used the Playback comand in my extensions.conf

Machine using HP DL380 Gen9 server Initially I got problem where boot hung at My IP 0.0.0.0 Then I referred to http://www.syslinux.org/archives/2015-June/023641.html And used the patch provided then it again hung but at different step Getting cached packet My IP 192.168.103.41 (hung here) >From /var/log/messages Oct 7 01:16:10 foreman in.tftpd[43905]: RRQ from 192.168.103.41 filename

hello list, I am trying to setup a PXE boot server. Below are the details of the server: OS : Fedora Core 5 32-bit DHCP : dhcp 4.1 TFTP : tftp-hpa-5.0 Number of NIC : 2 eth0 : IP : 192.168.100.17, Subnet : 255.255.255.0, Gateway : 192.168.100.1 eth1 : IP : 192.168.1.1, Subnet : 255.255.255.0, Gateway : 192.168.1.1 Client: OS : None, fresh machine Number of NIC : 2 Intel Gigabit eth0 of server

Anyone else seeing problems doing pxe boots off the latest dag/rpmforge syslinux packages? Versions 3.35 works, doing the tftp request like this: Jun 18 06:01:19 boothost in.tftpd[25947]: RRQ from 172.16.0.26 filename /centos5-i386/pxelinux.0 Jun 18 06:01:19 boothost in.tftpd[25947]: tftp: client does not accept options Jun 18 06:01:19 boothost in.tftpd[25948]: RRQ from 172.16.0.26

Hi, i'm trying to boot an 135mb acronis iso image with syslinux but have no luck, client gets stuck[1] a few seconds after selecting the image - i used linux memdisk initrd acronis/acronis_home_2010_multi.iso append iso tftpd-log shows: Mar 25 14:45:15 smbsrv in.tftpd[18837]: RRQ from 192.168.0.102 filename pxelinux.cfg/default Mar 25 14:45:15 smbsrv in.tftpd[18838]: RRQ from 192.168.0.102

Gene wrote: > On Wed, Oct 7, 2015 at 7:58 AM, Ashish, Shivendra <shivendra.ashish at hpe.com> wrote: >> Still getting error >> >> Disable uderdefault address > > 1) I'm presuming this is actually "disable UseDefaultAddress" > >> Core_udp_sento: udp->configure unsuccessful >> >> This message lopping in console > > Not

I've found a problem, and I think it is in syslinux (specifically when it tries to load ldlinux.e64 under hyper-V). I have a physical computer with a Gigabyte GA-P85-D3 motherboard that successfully pxeboots using the EFI images, and I hold that up as exhibit 1 that my deployment environment works. It also implies that the syslinux.efi image works in some cases, but not in all. My Hyper-V