List Info

Thread: Opal: SIP port question




Opal: SIP port question
country flaguser name
United States
2007-05-09 08:25:12
Good morning,
    Is there a way to force the simpleopal applicatino
(2.2.4) to send 
out INVITES and REGISTER traffic out port 5060?  I noticed
that when I 
regisiter with a SIP Registrar server, all traffic seems to
go out on 
psuedo-random udp ports.  In order to debug an issue I'm
having with 
Registrar server it would be very helpful to force the
traffic onto the 
well known port (5060) but I don't see a way to do this. 
Even if I bind 
my listemer to a specifice IP/port, the outbound traffic
never goes out 
5060.  I'm not concerned about the subsequent RTP traffic,
just the 
INVITES and REGISTERS.  Any suggestions?


------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Openh323-devel mailing list
Openh323-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openh323
-devel

Re: Opal: SIP port question
country flaguser name
Norway
2007-05-09 09:17:59
Hello,

Currently it is not possible to use port 5060 for sending
out PDUs.  
This is a known problem / limitation in the OPAL SIP stack,
and the  
problem will be fixed soon hopefully.

Hannes

On 9. Mai 2007, at 15:25, Chris Golas wrote:

> Good morning,
>     Is there a way to force the simpleopal applicatino
(2.2.4) to send
> out INVITES and REGISTER traffic out port 5060?  I
noticed that when I
> regisiter with a SIP Registrar server, all traffic
seems to go out on
> psuedo-random udp ports.  In order to debug an issue
I'm having with
> Registrar server it would be very helpful to force the
traffic onto  
> the
> well known port (5060) but I don't see a way to do
this.  Even if I  
> bind
> my listemer to a specifice IP/port, the outbound
traffic never goes  
> out
> 5060.  I'm not concerned about the subsequent RTP
traffic, just the
> INVITES and REGISTERS.  Any suggestions?
>
>
>
------------------------------------------------------------
---------- 
> ---
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2
express and take
> control of your XML. No limits. Just data. Click to get
it now.
> http://sourcefor
ge.net/powerbar/db2/
> _______________________________________________
> Openh323-devel mailing list
> Openh323-devellists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openh323
-devel


------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Openh323-devel mailing list
Openh323-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openh323
-devel

Re: Opal: SIP port question
country flaguser name
Spain
2007-05-09 09:22:39
In Opal Manager you can use SetUDPPorts, SetTCPPorts ...
functions to set
the ports you want.

-----Mensaje original-----
De: openh323-devel-bounceslists.sourceforge.net
[mailto:openh323-devel-bounceslists.sourceforge.net] En
nombre de Chris
Golas
Enviado el: miércoles, 09 de mayo de 2007 15:25
Para: openh323-devellists.sourceforge.net
Asunto: [Openh323-devel] Opal: SIP port question

Good morning,
    Is there a way to force the simpleopal applicatino
(2.2.4) to send 
out INVITES and REGISTER traffic out port 5060?  I noticed
that when I 
regisiter with a SIP Registrar server, all traffic seems to
go out on 
psuedo-random udp ports.  In order to debug an issue I'm
having with 
Registrar server it would be very helpful to force the
traffic onto the 
well known port (5060) but I don't see a way to do this. 
Even if I bind 
my listemer to a specifice IP/port, the outbound traffic
never goes out 
5060.  I'm not concerned about the subsequent RTP traffic,
just the 
INVITES and REGISTERS.  Any suggestions?


------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Openh323-devel mailing list
Openh323-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openh323
-devel


------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Openh323-devel mailing list
Openh323-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openh323
-devel

Re: Opal: SIP port question
country flaguser name
United States
2007-05-09 09:28:04
Hannes,
    Thanks for your help.

Hannes Friederich wrote:
ee.ethz.ch">
Hello,

Currently it is not possible to use port 5060 for sending out PDUs.  
This is a known problem / limitation in the OPAL SIP stack, and the  
problem will be fixed soon hopefully.

Hannes


On 9. Mai 2007, at 15:25, Chris Golas wrote:

  
Good morning,
    Is there a way to force the simpleopal applicatino (2.2.4) to send
out INVITES and REGISTER traffic out port 5060?  I noticed that when I
regisiter with a SIP Registrar server, all traffic seems to go out on
psuedo-random udp ports.  In order to debug an issue I'm having with
Registrar server it would be very helpful to force the traffic onto  
the
well known port (5060) but I don't see a way to do this.  Even if I  
bind
my listemer to a specifice IP/port, the outbound traffic never goes  
out
5060.  I'm not concerned about the subsequent RTP traffic, just the
INVITES and REGISTERS.  Any suggestions?


---------------------------------------------------------------------- 
---
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________

Openh323-devel mailing list
lists.sourceforge.net">Openh323-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openh323-devel
    


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________

Openh323-devel mailing list
lists.sourceforge.net">Openh323-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openh323-devel

  
Re: Opal: SIP port question
country flaguser name
Norway
2007-05-09 09:39:33
On 9. Mai 2007, at 16:22, Fernando Sanchez wrote:

> In Opal Manager you can use SetUDPPorts, SetTCPPorts
... functions  
> to set
> the ports you want.

Yes, but it still isn't possible to use port 5060 at the
moment. At  
launch, Opal uses sockets with port 5060 to listen for
incoming PDUs.  
When trying to send PDUs, the current code will use a fresh
socket.  
Since port 5060 is already blocked, it will use another
socket.


------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Openh323-devel mailing list
Openh323-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openh323
-devel

[1-5]

about | contact  Other archives ( Real Estate discussion Medical topics )