Re: [Seagull-users] question about SIP and H.248 with seagull

[Boulkroune, O. (Non-HP:A. Origin) <oli...@hp...>]

Hi,

I would say yes. You can try to use one Seagull SIP instance with two =
channels (one for each SIP client), synchronized (using the synchro =
protocol) with a h248 seagull instance.=20
As this is no trivial test case and you are not familiar with seagull, =
you will probably need time to have it work properly.=20

Regards,

Olivier Boulkroune
=20
-----Message d'origine-----
De=A0: gul...@li... =
[mailto:gul...@li...] De la part de Sridhar
Envoy=E9=A0: lundi 8 octobre 2007 10:39
=C0=A0: gul...@li...
Objet=A0: [Seagull-users] question about SIP and H.248 with seagull

hi all,
i'm pretty new to seagull (i read about it online for the first time
yesterday), and have spent a good part of today going through the
mailing list archives. i haven't been able to find an answer to my
question, so i hope someone on the list can help me..

my test network topology is as follows (apologies for the bad ASCII =
diagram)...


SIP client #1 --------------------------------------|
                                                         |
Media Gateway Controller --------- IP router / media gateway
                                                         |
SIP client #2 --------------------------------------|

SIP clients #1 and #2 need to establish a SIP call session between
each other through the IP router / media gateway, which is the device
under test. client #1 sends the INVITE to the media gateway
controller, which forwards the INVITE to client #2 after changing the
src IP and the SDP info in the INVITE (so that client #1 will
eventually send RTP to the IP router / media gateway's IP). Likewise,
when client #2 sends SIP responses back to the media gateway
controller, it should modify the src IP and SDP info in the response
and forward it back to client #1.

The Media Gateway Controller also needs to use H.248/Megaco to talk to
the IP router / media gateway in order to allow the RTP flow between
client #1 and client #2.

I'd like to use real-world SIP clients for #1 and #2. can i use
seagull for the media gateway controller? it has to talk SIP with both
clients #1 and #2, and also talk H.248/Megaco with the IP router.

I saw some emails about multi-protocol scenarios in seagull, but i'm
not sure if that's to be used in this case. i'd appreciate it if
someone on the list can tell me if seagull can be used for what i'm
trying to do. i'm planning to set up seagull in my lab tomorrow (it's
past midnight now), but thought i'll send a quick email to see if
someone has tried this already.

thanks in advance
sridhar

-------------------------------------------------------------------------=

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Gull-users mailing list
Gul...@li...
https://lists.sourceforge.net/lists/listinfo/gull-users