Re: [Opalvoip-user] Lifesize -> Ekiga 4.0 call are unsuccesful on Windows.
Brought to you by:
csoutheren,
rjongbloed
Menu
▾
▴
Re: [Opalvoip-user] Lifesize -> Ekiga 4.0 call are unsuccesful on Windows.
|
From: Robert J. <ro...@vo...> - 2012-11-29 22:23:30
|
I don't think the DNS name lookup error is a serious issue. They do often happen for legitimate reasons. The easiest way to determine if you have a legal IP address is to convert it, but that then causes the trace log. The real issue is why is it trying to set the audio player device to "EKIGA". That does not seem correct to me. I believe Ekiga must be setting this, I cannot see PTLib or OPAL having the string "EKIGA" anywhere in it. *Robert Jongbloed* /OPAL/OpenH323/PTLib Architect and Co-founder./ Commercial support at http://www.voxlucida.com.au On 30/11/2012 1:17 AM, Eugen Dedu wrote: > So with the patched version, the error on sound device disappeared, but > the one on DNS name did not. Do you know how to remove that too, Robert? > > 2012/11/29 11:28:33.046 0:20.919 Opal Answer:1844 OpalMan > Searching for route "h323:admin ip$91.65.78.163:1720" > 2012/11/29 11:28:33.046 0:20.919 Opal Answer:1844 OpalMan Did > not match regex "^sip:.* .*$" ("sip:.*") > 2012/11/29 11:28:33.047 0:20.920 Opal Answer:1844 OpalMan Did > not match regex "^pc:.* .*$" ("pc:.*") > 2012/11/29 11:28:33.047 0:20.920 Opal Answer:1844 OpalMan > Matched regex "^h323:.* .*$" ("h323:.*") > 2012/11/29 11:28:33.047 0:20.920 Opal Answer:1844 Socket > Illegal RFC952 characters in DNS name "ip$91.65.78.163" > 2012/11/29 11:28:33.047 0:20.920 Opal Answer:1844 OpalMan Set > up connection to "pc:*" > 2012/11/29 11:28:33.052 0:20.925 Opal Answer:1844 PCSS Sound > player device set to "EKIGA" > > Eugen > > On 29/11/12 13:03, IMMO WETZEL wrote: >> Hi Eugen, >> >> I did my best and tried the new version. Seems to be better but not successful. I wasn’t able to handup the phone at all on the ekiga side. If necessary/helpful I can show you this with a gotomeeting session tomorrow. >> >> On 29/11/12 10:27, IMMO WETZEL wrote: >>> Hi, >>> >>> As soon as I get a binary I can try this out. >>> >>> Immo >>> >>> -----Original Message----- >>> From: Eugen Dedu [mailto:Eug...@pu...] >>> Sent: Donnerstag, 29. November 2012 10:06 >>> To: opalvoip-user >>> Subject: Re: [Opalvoip-user] Lifesize -> Ekiga 4.0 call are unsuccesful on Windows. >>> >>> You are right, ekiga has: >>> manager.AddRouteEntry("h323:.* = pc:<db>"); >>> >>> So it should be changed to: >>> manager.AddRouteEntry("h323:.* = pc:*"); is that right? >>> >>> Immo, could you test this change (in >>> lib/engine/components/opal/h323-endpoint.cpp file)? >>> >>> Eugen >>> >>> On 28/11/12 23:58, Robert Jongbloed wrote: >>>> Problem is in the Ekiga route table. Whatever is on the right hand side of: >>>> >>>> Matched regex "^h323:.* .*$" ("h323:.*") >>>> >>>> >>>> is incorrect. >>>> >>>> I am guessing Ekiga has "h323:.* = pc:<da>", it should be something >>>> like >>>> "h323:.* = pc:*" or the "address" part of the incoming H.323 call is >>>> used as the sound device, as in: >>>> >>>> Sound player device "ip$91.91.78.163:1720" does not exist, call aborted. >>>> >>>> which will not work. >>>> >>>> *Robert Jongbloed* >>>> /OPAL/OpenH323/PTLib Architect and Co-founder./ Commercial support at >>>> http://www.voxlucida.com.au >>>> >>>> On 29/11/2012 9:05 AM, IMMO WETZEL wrote: >>>>> Hello, >>>>> >>>>> Eugen ask me to write again to this list. >>>>> >>>>> I tried to setup a call from our company internal lifesize Express >>>>> videoConfBox to my Ekiga host @home. But it fails. >>>>> >>>>> EKIGA Version is 4.0.0 downloaded today >>>>> >>>>> The main problem I saw is the ip address analysis. This seemsto be >>>>> somehow wrong. >>>>> >>>>> 2012/11/28 14:29:18.911 0:35.873 Opal Answer:1248 EndPoint Incoming >>>>> connection >>>>> >>>>> 2012/11/28 14:29:18.911 0:35.874 Opal Answer:1248 OpalMan OnIncoming >>>>> connection Call[C8787c87e1]-EP<h323>[tcp$193.158.105.118:63908/5915] >>>>> >>>>> 2012/11/28 14:29:18.911 0:35.874 Opal Answer:1248 Call >>>>> GetOtherPartyConnection >>>>> Call[C8787c87e1]-EP<h323>[tcp$193.158.105.118:63908/5915] >>>>> >>>>> 2012/11/28 14:29:18.912 0:35.874 Opal Answer:1248 OpalMan Searching >>>>> for route "h323:admin ip$91.91.78.163:1720" >>>>> >>>>> 2012/11/28 14:29:18.912 0:35.874 Opal Answer:1248 OpalMan Did not >>>>> match regex "^sip:.* .*$" ("sip:.*") >>>>> >>>>> 2012/11/28 14:29:18.912 0:35.874 Opal Answer:1248 OpalMan Did not >>>>> match regex "^pc:.* .*$" ("pc:.*") >>>>> >>>>> 2012/11/28 14:29:18.912 0:35.874 Opal Answer:1248 OpalMan Matched >>>>> regex "^h323:.* .*$" ("h323:.*") >>>>> >>>>> 2012/11/28 14:29:18.912 0:35.874 Opal Answer:1248 Socket Illegal >>>>> RFC952 characters in DNS name "ip$91.91.78.163" >>>>> >>>>> 2012/11/28 14:29:18.912 0:35.875 Opal Answer:1248 OpalMan Set up >>>>> connection to "pc:ip$91.91.78.163:1720" >>>>> >>>>> 2012/11/28 14:29:18.921 0:35.883 Opal Answer:1248 PCSS Sound player >>>>> device "ip$91.91.78.163:1720" does not exist, call aborted. > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > VERIFY Test and improve your parallel project with help from experts > and peers. http://goparallel.sourceforge.net > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user |