On Tue, Dec 22, 2009 at 12:14 PM, Dale Worley <[email protected]> wrote:
> On Tue, 2009-12-22 at 09:24 -0600, M. Ranganathan (JIRA) wrote:
>> Each log record has a the relevant information and it looks like this:
>> ----Remote Host:192.168.5.243---- Port: 5060----
>> We need to extract that information from the file and place it as
>> either a separate element or change the destination address (or source
>> address in the case of inbound packets) in the generated tag.
>
> In regard to the first step of processing, turning the .log file into a
> siptrace file, there is a problem:  The syslog provides the remote IP
> address and port, but it does not provide the local IP address and port.
>
> In the example in XX-7318 (frame 1 of merged.xml, frame 2648 of
> sipxpbx/sipXproxy.{xml,log}), we know that the remote (source) host:port
> is 192.168.5.242:5060, but we don't know the local (destination)
> host:port.  So the siptrace that is generated is:
>
>                <branchNode>
>                        <branchIdSet>
>                                <branchId>z9hG4bK3795dcaa27543A03</branchId>
>                        </branchIdSet>
>                        <time>2009-12-22T05:58:32.506806Z</time>
>                        <source>192.168.5.242:5060</source>
>                        <destination>sipxpbx-SipXProxy</destination>
>                        <sourceAddress>192.168.5.242:5060</sourceAddress>
>                        
> <destinationAddress>sipxpbx-SipXProxy</destinationAddress>
>                        
> <transactionId>1,[email protected],BE00146F-4F79F97C,</transactionId>
>                        <method>REGISTER</method>
>                        <frameId>2648</frameId>
>                        <message><![CDATA[ [...]
>        ]]></message>
>                </branchNode>
>
> If we had a log entry for the sender of the message, siptrace-merge
> could get the destination address from there.  (But it doesn't now, it
> performs a test incorrectly.)
>
> One alternative would be to adjust the generation of this log message to
> include the local host:port, which shouldn't be too difficult.
>
> Dale


I actually do not need the local IP address. I just need the
destination IP address for outbound requests. If this terminology is
confusing, we can use the term "remoteAdderess"

This is already present in the log record for example:

TCP SIP User Agent sent message:\n----Remote Host:192.168.5.240----
Port: 5070----\n

If this information can be extracted from the file and placed in the
XML that would be most helpful.

Regards,

Ranga

>
>
> _______________________________________________
> sipx-dev mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
> sipXecs IP PBX -- http://www.sipfoundry.org/
>



-- 
M. Ranganathan
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to