Hi Girish, All

...

I have to implement some advanced SIP services

like

...

parallel/sequential ringing, of all registered sip

and

...

PSTN phones.

Can SER support that kind of functionality ?

You can use use the command append_branch() to implement parallel forking with SER. SER doesn't have any built-in mechanism to do sequential forking. However, you can use failure routes in your script to implement this feature.

Sorry for asking such trivial question for you, but in the seruser.pdf there is the following WARNING: ----------------------------------------------------------------- ser’s request processing language allows to make request decisions based on current URI. When a request if forked to multiple destinations, only the first branch’s URI is used as input for script processing. This might lead to unexpected results. Whenever a URI resolves to multiple different next-hop URIs, only the first is processed which may result in handling not appropriate for the other branch. For example, a URI might resolve to an IP phone SIP address and PSTN gateway SIP address. If the IP phone address is the first, then script execution ignores the second branch. If a script includes checking gateway address in request URI, the checks never match. That might result in ignoring of gateway admission control rules or applying them unnecessarily to non-gateway destinations. ------------------------------------------------------------

Doent this limination affect's the append_branch workaround ?

____________________________________________________________ Do You Yahoo!? Αποκτήστε τη δωρεάν @yahoo.gr διεύθυνση σας στο http://www.otenet.gr

Hello, some serial forking can be implemented using the AVPOPS module with CVS head SER version. Take a look at the example from http://www.voice-system.ro/docs/avpops/ar01s08.html#ex_serial_forking

It may help you.

Salutari, Ramona

Girish wrote:

Hello,

--- "G. P." pagomen2001@yahoo.gr wrote:

...

Hi all,

I have to implement some advanced SIP services like parallel/sequential ringing, of all registered sip and PSTN phones.

Can SER support that kind of functionality ?

You can use use the command append_branch() to implement parallel forking with SER. SER doesn't have any built-in mechanism to do sequential forking. However, you can use failure routes in your script to implement this feature.

...

Thanks George

Regards,

===== Girish Gopinath gr_sh2003@yahoo.com

__________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Hello,

comments inline ...

Girish wrote:

Hello,

--- Elena Ramona Modroiu ramona@voice-system.ro wrote:

...

Hello, some serial forking can be implemented using the AVPOPS module with CVS head SER version. Take a look at the example from http://www.voice-system.ro/docs/avpops/ar01s08.html#ex_serial_forking

It may help you.

Thanks for this info. I read only the serial forking section. A few questions...

From the code snippet given in the above mentioned doc, i can see that the different addresses can be set for forking initially. But it again uses failure routes. We implement serial forking using the existing failure routing mechanisms. Is there any advantage of using this new approach apart from setting the initial fork list?

I don't know how is your implementation, with this approach you can load the destination addresses from database as well as specifying them directly in config file or from a module. Otherwise the failure route mechanism should be the same.

I guess it will make processing faster, in case the records are taken from DB or they are set using a custom-built module. Am i correct?

yes, but as I said above you can set them also directly in the config file.

The document says that "There are no limitations", but in your mail you have stated that "some serial forking can be implemented". Can you explain that a bit?

The "no limitations" statement is about the way of setting or resetting the destination set. I said "some serial forking" because, for example, it doesn't support explicitly priorities for destination addresses (from database the records are loaded in the order returned by a query after the name).

Then, pardon me for my ignorance... but what is 'Salutari' ??

"salutari" is the Romanian word for "regards". You can check it at www.dictionare.com .

Salutari :), Ramona

Hello,

On Thu, Nov 11, 2004 at 09:17:25PM -0800, Girish wrote:

Hello,

--- Elena Ramona Modroiu ramona@voice-system.ro wrote:

...

...

The document says that "There are no limitations", but in your mail you have stated that "some

serial forking can be implemented". Can you explain that a bit?

...

The "no limitations" statement is about the way of setting or resetting the destination set. I said "some serial forking" because, for example, it doesn't support explicitly priorities for destination addresses (from database the records are loaded in the order returned by a query after the name).

OK. So if I have a module function 'set_fork_list()' as given in the doc, which gets the fork list may be with an sql query - something like this:

SELECT uri_to_branch, priority FROM fork_list WHERE actual_uri = 'abc@xyz.com' ORDER BY priority DESC;

Will that overcome the limitation? I assume that DESC is required since the AVP list is arranged backwards. Right?

It might be better ASC, you have to add first the one with the lowest priority.

Salutari, Ramona

...

"salutari" is the Romanian word for "regards". You can check it at www.dictionare.com .