Hi, starting with GnuGk 2.2.3, we had a switch SignalCallID=1 that would turn on the call-id at the end of the status port events. That switch was removed in GnuGk 2.2.7 and now you always get the call-id. As a general rule: Applications have to ignore fields at the end of status port events that they don't know about. New GnuGk versions won't change the meaning of fields, but will sometimes add more information at the end. Regards, Jan Kjell Gustafsson wrote: > Hi > > We have been using GnuGK 2.2.5 and have an external application that > recieve > a RouteRequets from the statusport on the GnuGK, performs some lookups > and responds with a RouteResponse/RouteReject to the GnuGK. > > We have recently upgraded to 2.2.8 since it seems to hold some > interresting new > features. After the upgrade we found that the format of the route > request has > changed and this causes our application not to work anymore. > > In 2.2.5 it looked like this: > > RouteRequest|172.31.10.100:1720|9755_endp|2890|9412274801002| > 9412101811002:dialedDigits; > > > In 2.2.8 it has changed to this: > > RouteRequest|192.168.255.111:1720|2154_endp|13621|9412274801001| > 9412101811001:dialedDigits|02-b2-38-ac- > b8-8a-2c-16-00-7c-56-34-34-34-34-ef|unknown; > > > Have someone else come across this problem? > > Is there a configuration parameter that causes this new behaviour? If > so - which one? > > Or do we have to change our application to handle the new format? > > /Kjelle -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
