Hi Marcello!

does serialize_branches() work if you add the branches in openser.cfg? E.g. you could use append_branch(......) to add the branches manually and then try serialize_branches() .

klaus

Marcello Lupo schrieb:
Hi to all,
i made some other tests about this issue and i think it can be a bug somewhere in the serialize_branches() executed after exec_dset().
I made tests changing the qvalue to format:

q=1.0
q=0.1
q=1

both with \n and \r\n at the end of lines and serialize_branches() give me all the time the same result:

DEBUG:serialize_branches: nothing to do - all same q!

But if i got only one line from exec_dset() it give me:

DEBUG:serialize_branches: nothing to do - no branches!

So it see the difference between one line and more lines from exec_dset() .
Please help me with this issue i really need serial forking from exec_dset() to work.

Thanks,
Bye,
Marcello


Marcello Lupo wrote:
Hi to all,
i'm using openser 1.2.2 no tls and i use exec_dset to get list of gateways in destination set to be serialized.

After execution of exec_dset i get in output:

sip:[EMAIL PROTECTED]:5062;q=0.2
sip:[EMAIL PROTECTED]:5060;q=0.1

$ds become : Contact: sip:[EMAIL PROTECTED]:5062;q=0.2, sip:[EMAIL PROTECTED]:5060;q=0.1

RURI become: sip:[EMAIL PROTECTED]:5062;q=0.2

$bR become: sip:[EMAIL PROTECTED]:5060;q=0.1

All seems to be fine but when i run serialize_branches() i get:

DEBUG:serialize_branches: nothing to do - all same q!

Any ideas on what i'm missing?

May be something in the output of exec_dset??
I'm using the \n between lines in my custom LCR scripts to get gateways from DB.

Thanks,
Bye,
Marcello


_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users




_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users

Reply via email to