15 Feb
2013
15 Feb
'13
2:45 p.m.
Hello,
Is there any reason why I couldn't use the existing siptrace() function
in event_route[msrp:frame-in] to relay all MSRP messages to a SIP
Capture node?
Will the SIP Capture node handle receiving these messages?
What will end up in the WebHomer display in these cases?
Regards,
Peter
15 Feb
15 Feb
2:50 p.m.
Also, what about stuff from event_route[xhttp:request]?
On 15/02/13 14:45, Peter Dunkley wrote:
Hello,
Is there any reason why I couldn't use the existing siptrace()
function in event_route[msrp:frame-in] to relay all MSRP messages to a
SIP Capture node?
Will the SIP Capture node handle receiving these messages?
What will end up in the WebHomer display in these cases?
Regards,
Peter
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
3:22 p.m.
Hi,
As far as I know, although making siptrace encapsulate different types
of messages is not something very difficult, the sipcapture module is
developed to write SIP messages into database.
Webhomer 3 reads SIP-related data from DB, so it displays only SIP.
Regards,
Dragos
On 02/15/2013 04:45 PM, Peter Dunkley wrote:
Hello,
Is there any reason why I couldn't use the existing siptrace() function
in event_route[msrp:frame-in] to relay all MSRP messages to a SIP
Capture node?
Will the SIP Capture node handle receiving these messages?
What will end up in the WebHomer display in these cases?
Regards,
Peter
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
3:30 p.m.
I know that the HEP3 protocol is designed to handle different message
types, so I am curious as to whether the implementation of the capture
node can handle it.
Also, if the capture node can handle it and it does go into the DB will
it cause problems for webhomer, or will webhomer simply ignore non-SIP
entries (which would be absolutely fine for my use-case)?
Regards,
Peter
On 15/02/13 15:22, Dragos Dinu wrote:
Hi,
As far as I know, although making siptrace encapsulate different types
of messages is not something very difficult, the sipcapture module is
developed to write SIP messages into database.
Webhomer 3 reads SIP-related data from DB, so it displays only SIP.
Regards,
Dragos
On 02/15/2013 04:45 PM, Peter Dunkley wrote:
Hello,
Is there any reason why I couldn't use the existing siptrace() function
in event_route[msrp:frame-in] to relay all MSRP messages to a SIP
Capture node?
Will the SIP Capture node handle receiving these messages?
What will end up in the WebHomer display in these cases?
Regards,
Peter
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
3:47 p.m.
Sipcapture can't handle it, because it parses the data as SIP message.
If sipcapture would be able to handle it and get it into the DB,
Webhomer will be able to show it, because it shows all the entries that
you write into the DB.
You can, for example, write the MSRP message into the 'msg' column of
the table and leave all the other sip-related columns blank. Webhomer
will display the data just like that. Think of Webhomer as a
user-interface to see everything that is in there (and to search data).
Hope it helps,
Dragos
On 02/15/2013 05:30 PM, Peter Dunkley wrote:
I know that the HEP3 protocol is designed to handle
different message
types, so I am curious as to whether the implementation of the capture
node can handle it.
Also, if the capture node can handle it and it does go into the DB will
it cause problems for webhomer, or will webhomer simply ignore non-SIP
entries (which would be absolutely fine for my use-case)?
Regards,
Peter
On 15/02/13 15:22, Dragos Dinu wrote:
Hi,
As far as I know, although making siptrace encapsulate different types
of messages is not something very difficult, the sipcapture module is
developed to write SIP messages into database.
Webhomer 3 reads SIP-related data from DB, so it displays only SIP.
Regards,
Dragos
On 02/15/2013 04:45 PM, Peter Dunkley wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
Is there any reason why I couldn't use the existing siptrace() function
in event_route[msrp:frame-in] to relay all MSRP messages to a SIP
Capture node?
Will the SIP Capture node handle receiving these messages?
What will end up in the WebHomer display in these cases?
Regards,
Peter
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
3:56 p.m.
OK. So sipcapture parses the messages itself instead of using the
Kamailio's message parsing (which does handle HTTP and MSRP)?
Regards,
Peter
On 15/02/13 15:47, Dragos Dinu wrote:
Sipcapture can't handle it, because it parses the
data as SIP message.
If sipcapture would be able to handle it and get it into the DB,
Webhomer will be able to show it, because it shows all the entries
that you write into the DB.
You can, for example, write the MSRP message into the 'msg' column of
the table and leave all the other sip-related columns blank. Webhomer
will display the data just like that. Think of Webhomer as a
user-interface to see everything that is in there (and to search data).
Hope it helps,
Dragos
On 02/15/2013 05:30 PM, Peter Dunkley wrote:
I know that the HEP3 protocol is designed to
handle different message
types, so I am curious as to whether the implementation of the capture
node can handle it.
Also, if the capture node can handle it and it does go into the DB will
it cause problems for webhomer, or will webhomer simply ignore non-SIP
entries (which would be absolutely fine for my use-case)?
Regards,
Peter
On 15/02/13 15:22, Dragos Dinu wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users Hi,
As far as I know, although making siptrace encapsulate different types
of messages is not something very difficult, the sipcapture module is
developed to write SIP messages into database.
Webhomer 3 reads SIP-related data from DB, so it displays only SIP.
Regards,
Dragos
On 02/15/2013 04:45 PM, Peter Dunkley wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
Is there any reason why I couldn't use the existing siptrace()
function
in event_route[msrp:frame-in] to relay all MSRP messages to a SIP
Capture node?
Will the SIP Capture node handle receiving these messages?
What will end up in the WebHomer display in these cases?
Regards,
Peter
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
4:01 p.m.
Actually, the sipcapture module does use the Kamailio message parsing.
It looks like only a few small changes will be required to make it
recognise and handle HTTP and MSRP.
I will look into doing this.
Regards,
Peter
On 15/02/13 15:56, Peter Dunkley wrote:
OK. So sipcapture parses the messages itself instead
of using the
Kamailio's message parsing (which does handle HTTP and MSRP)?
Regards,
Peter
On 15/02/13 15:47, Dragos Dinu wrote:
Sipcapture can't handle it, because it parses
the data as SIP message.
If sipcapture would be able to handle it and get it into the DB,
Webhomer will be able to show it, because it shows all the entries
that you write into the DB.
You can, for example, write the MSRP message into the 'msg' column of
the table and leave all the other sip-related columns blank. Webhomer
will display the data just like that. Think of Webhomer as a
user-interface to see everything that is in there (and to search data).
Hope it helps,
Dragos
On 02/15/2013 05:30 PM, Peter Dunkley wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users I know that the HEP3 protocol is designed to
handle different message
types, so I am curious as to whether the implementation of the capture
node can handle it.
Also, if the capture node can handle it and it does go into the DB will
it cause problems for webhomer, or will webhomer simply ignore non-SIP
entries (which would be absolutely fine for my use-case)?
Regards,
Peter
On 15/02/13 15:22, Dragos Dinu wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users Hi,
As far as I know, although making siptrace encapsulate different types
of messages is not something very difficult, the sipcapture module is
developed to write SIP messages into database.
Webhomer 3 reads SIP-related data from DB, so it displays only SIP.
Regards,
Dragos
On 02/15/2013 04:45 PM, Peter Dunkley wrote:
> Hello,
>
> Is there any reason why I couldn't use the existing siptrace()
> function
> in event_route[msrp:frame-in] to relay all MSRP messages to a SIP
> Capture node?
>
> Will the SIP Capture node handle receiving these messages?
>
> What will end up in the WebHomer display in these cases?
>
> Regards,
>
> Peter
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
5:09 p.m.
Peter, before need to implement HEPv3 into siptrace module. Currently it has
only HEPv1/v2 support.
Can you please contact me in gtalk, we can do it together step by step.
Wbr,
Alexandr
-----Original Message-----
From: sr-users-bounces(a)lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Peter Dunkley
Sent: Friday, February 15, 2013 5:02 PM
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] siptrace/sipcapture and MSRP
Actually, the sipcapture module does use the Kamailio message parsing.
It looks like only a few small changes will be required to make it recognise
and handle HTTP and MSRP.
I will look into doing this.
Regards,
Peter
On 15/02/13 15:56, Peter Dunkley wrote:
OK. So sipcapture parses the messages itself instead
of using the
Kamailio's message parsing (which does handle HTTP and MSRP)?
Regards,
Peter
On 15/02/13 15:47, Dragos Dinu wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Sipcapture can't handle it, because it parses
the data as SIP message.
If sipcapture would be able to handle it and get it into the DB,
Webhomer will be able to show it, because it shows all the entries
that you write into the DB.
You can, for example, write the MSRP message into the 'msg' column of
the table and leave all the other sip-related columns blank. Webhomer
will display the data just like that. Think of Webhomer as a
user-interface to see everything that is in there (and to search data).
Hope it helps,
Dragos
On 02/15/2013 05:30 PM, Peter Dunkley wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users I know that the HEP3 protocol is designed to
handle different
message types, so I am curious as to whether the implementation of
the capture node can handle it.
Also, if the capture node can handle it and it does go into the DB
will it cause problems for webhomer, or will webhomer simply ignore
non-SIP entries (which would be absolutely fine for my use-case)?
Regards,
Peter
On 15/02/13 15:22, Dragos Dinu wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users Hi,
As far as I know, although making siptrace encapsulate different
types of messages is not something very difficult, the sipcapture
module is developed to write SIP messages into database.
Webhomer 3 reads SIP-related data from DB, so it displays only SIP.
Regards,
Dragos
On 02/15/2013 04:45 PM, Peter Dunkley wrote:
> Hello,
>
> Is there any reason why I couldn't use the existing siptrace()
> function in event_route[msrp:frame-in] to relay all MSRP messages
> to a SIP Capture node?
>
> Will the SIP Capture node handle receiving these messages?
>
> What will end up in the WebHomer display in these cases?
>
> Regards,
>
> Peter
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> list sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
4169
days inactive
4169
days old
7 comments
3 participants
participants (3)
-
Alexandr Dubovikov -
Dragos Dinu -
Peter Dunkley