Hello Avin, Please see my comments inline.
> As end user, h323id/e164 will have priority than ip, to make a call. > As wholesale provider/your case, IP address have priority than h323id/164. > In corporating your changes, will break the end user case. So we will have > > to add your changes, without breaking first case. > Other reason, comparing ip first, someone might be using two phones on > > >> > same ip, than we don't whom we are referring to. I suppose you are right. If we set the IP checking last, it will still be good for the wholesale case, since there will be no match with E146/h323id... > What I understood, You want to make a call on to IP address, instead of > >> > h323id/e164 alias. > You can set the IP address for h323id/e164 number in config file. > How the call is originated in your case. Are you making call or responding >> > to incoming call? I was referring to the incoming calls. The outgoing calls had no problem identifying peers/users, etc. > Another solution: > As per standard, you can use peer->url to compare it. Adding 'url' > >> >>> > comparing in find_peer() will be alright. > And defining 'url' in config file, instead of h323id/e164. I didn't know that we could define a URL in the ooh323.conf file. I'll take a look at it. However, if we can match the IP address of the incoming call even if it is checked last, then there is no problem even in the wholesale case, where all that is needed is the identification of the incoming call based on IP address. Best regards, Vlasis. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ ooh323c-devel mailing list ooh323c-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ooh323c-devel
