24 Oct
2006
24 Oct
'06
4:34 p.m.
hello, all
someone can tell me how i can configurate yate client
to work which openser when i make a config the account
cant register please help
___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo!
Questions/Réponses
http://fr.answers.yahoo.com
26 Oct
26 Oct
11:35 a.m.
Hello,
never used Yate, but it should have some fields for username, proxy
address and password in SIP settings. Watch the network on your sip
server to see if yate sends register messages (ngrep -qt -d any port 5060).
Cheers,
Daniel
On 10/24/06 16:34, sinclair fils wrote:
hello, all
someone can tell me how i can configurate yate client
to work which openser when i make a config the account
cant register please help
___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo!
Questions/Réponses
http://fr.answers.yahoo.com
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
29 Oct
29 Oct
10:41 a.m.
New subject: [Users] Failure route psuedo variables
Hello,
I have a failure route setup and armed using t_on_failure.
When I attempt to interogate $rr or $rs in the failure route they are
always null.
$rU is set which makes me wonder am I only able to access pseudo
variables for requests.
I would like to generate some specialized logging based on the status
code ( 487, 404 etc ) but $rs doesn't give me the status.
I also tried t_check_status(487) but it does not work even when it was a
487 message that triggered the failure route.
Am I missing something?
Thanks
t.r.
6:36 p.m.
New subject: [Users] Failure route psuedo variables
See my post of 10/27:
http://openser.org/pipermail/users/2006-October/007441.html
Same question. However, t_on_failure works for me. I think you want to
quote the code: t_check_status("487").
Let me know if you have any luck getting $rr or $rs to work.
I wonder if there's a way to have tm pass this info along in an avp?
/a
T.R. Missner wrote:
Hello,
I have a failure route setup and armed using t_on_failure.
When I attempt to interogate $rr or $rs in the failure route they are
always null.
$rU is set which makes me wonder am I only able to access pseudo
variables for requests.
I would like to generate some specialized logging based on the status
code ( 487, 404 etc ) but $rs doesn't give me the status.
I also tried t_check_status(487) but it does not work even when it was a
487 message that triggered the failure route.
Am I missing something?
Thanks
t.r.
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
6602
days inactive
6607
days old
3 comments
4 participants
participants (4)
-
Alan Crosswell -
Daniel-Constantin Mierla -
sinclair fils -
T.R. Missner