I'm trying to connect 2 GKs. Version 2.2.0 is used in both GK. GK_A has an EP registed to it with alias 1001, GK_B has an EP registed to it with alias 2001. In GK_B, I set GK_A as Permanent EP like [RasSrv::PermanentEndpoints] 192.168.2.218=GK_A;1 When I dial 1001 from 2001, I see an ACF from the status port, right after that I get a DCF. By tracing the log in GK_B, I get : ProxyChannel.cxx(1984) Q931 192.168.2.218:1720 DIDN'T ACCEPT THE CALL where 192.168.2.218 is the IP for GK_A. But in GK_A, nothing related to GK_B in the log. Please help me to find out the problem. Thanks.
correct me if I'm wrong, but you seem to be talking about GnuGK gatekeepers (H.323 devices). SER is a SIP device. Someone please tell me if there is a way to get SER to talk to H.323. I would be ecestatic if there were.
hwang@gaia.ecs.csus.edu wrote:
I'm trying to connect 2 GKs. Version 2.2.0 is used in both GK. GK_A has an EP registed to it with alias 1001, GK_B has an EP registed to it with alias 2001. In GK_B, I set GK_A as Permanent EP like [RasSrv::PermanentEndpoints] 192.168.2.218=GK_A;1 When I dial 1001 from 2001, I see an ACF from the status port, right after that I get a DCF. By tracing the log in GK_B, I get : ProxyChannel.cxx(1984) Q931 192.168.2.218:1720 DIDN'T ACCEPT THE CALL where 192.168.2.218 is the IP for GK_A. But in GK_A, nothing related to GK_B in the log. Please help me to find out the problem. Thanks.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi
I am no authority on this but the only way I have heard you can do it today is by using asterisk - but you have to live with how asterisk munges the codec negotiation. In other words it may not work for Video.
We are working on getting one of these configurations work so we can find out the limitations.
But if someone has it working and documented then we would be very interested as well.
Stephen
Bruce Ferrell wrote:
correct me if I'm wrong, but you seem to be talking about GnuGK gatekeepers (H.323 devices). SER is a SIP device. Someone please tell me if there is a way to get SER to talk to H.323. I would be ecestatic if there were.
hwang@gaia.ecs.csus.edu wrote:
I'm trying to connect 2 GKs. Version 2.2.0 is used in both GK. GK_A has an EP registed to it with alias 1001, GK_B has an EP registed to it with alias 2001. In GK_B, I set GK_A as Permanent EP like [RasSrv::PermanentEndpoints] 192.168.2.218=GK_A;1 When I dial 1001 from 2001, I see an ACF from the status port, right after that I get a DCF. By tracing the log in GK_B, I get : ProxyChannel.cxx(1984) Q931 192.168.2.218:1720 DIDN'T ACCEPT THE CALL where 192.168.2.218 is the IP for GK_A. But in GK_A, nothing related to GK_B in the log. Please help me to find out the problem. Thanks.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
First I'd eliminate a dialplan issue by registering both endpoints to the same gatekeeper. This will eliminate any of the obvious cross zone issues. Assuming this works then the next thing I'd try is to place an inter-zone call using the fully qualified h.323 e164 address or alias depending upon the dialplan in use. You didn't mention anything about the zones. I'm assuming the gatekeepers are responsible for different non-overlapping zones and the endpoints register correctly.
Good luck, Steve
hwang@ecs.csus.edu wrote:
I'm trying to connect 2 GKs. Version 2.2.0 is used in both GK. GK_A has an EP registed to it with alias 1001, GK_B has an EP registed to it with alias 2001. In GK_B, I set GK_A as Permanent EP like [RasSrv::PermanentEndpoints] 192.168.2.218=GK_A;1 When I dial 1001 from 2001, I see an ACF from the status port, right after that I get a DCF. By tracing the log in GK_B, I get : ProxyChannel.cxx(1984) Q931 192.168.2.218:1720 DIDN'T ACCEPT THE CALL where 192.168.2.218 is the IP for GK_A. But in GK_A, nothing related to GK_B in the log. Please help me to find out the problem. Thanks.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers