[OpenSER-Devel] [SEAS] Problem with Registration of AS

[elias baixas]

Hello Rajat,

Actions Socket is used by the App Server to send OpenSER 'actions' to  
be performed (create new transaction, respond to request, etc.),
Events socket is used by OpenSER to inform AppServer of incoming  
messages/events to be processed by the App Server.
This could have been done using only one socket, but this way seemed  
more reasonable at design time, so that Actions and Events
were processed by a different process, and could be acknowledged  
independently.

This is  explained in SEAS documentation, openser/modules/seas/doc

when you register an AS, it needs to connect to both Action and Event  
sockets, and publish its AppServer name.
When SEAS sees the same AppServer name on both sockets, it considers  
the AppServer successfully registered.
the order in which the AppServer connects to Action/Event sockets is  
not relevant, but it must connect to both sockets
in order to start receiving Events.

The AppServer must register with the same name that is used in the  
OpenSER script when as_relay is invoked. That's the APpSErver name.

regards,

Elias


El 07/02/2008, a las 13:38, Rajat Dudeja escribió:

>
> Hi,
>
> I have following basic questions:
>
> 1. What does Event socket do?
>  i.e. What kind of data flows on Event Socket?
>
> 2. What does Action Socket do?
>    i.e. What kind of data flows on Event Socket?
>
> 3. Which socket should one use for registering an AS? To be more  
> elaborate,
> how registration process actually works?
>
> I'm not able to register my AS ( I fear I may not be using the correct
> socket for registration).
>
> I have
> Please help
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/devel