29 Sep
2004
29 Sep
'04
4:50 p.m.
Hello everyone.
Is there a way in my ser.cfg I can tell the difference between calls when a
user hangs up and when there is no answer by the called UA?
It seems to me that the return codes are the same, ie 487.
BUSY is OK because that returns 486.
I'm trying to figure out how to route calls to voice mail when there is no
answer only. I don't need to send the user to voice mail if the caller simply
hangs up. It's almost like RFC2543 needed to define return code 487 as NOANSWER
and a new code 488 as HUNGUP
Is there a way to accomplish this?
Regards,
Paul
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
30 Sep
30 Sep
3:04 a.m.
Is there a way in my ser.cfg I can tell the difference
between calls when a user hangs up and when there is no
answer by the called UA?
It seems to me that the return codes are the same, ie 487.
You can use t_check_status(...) to check for status code. For caller
hang-up, ser will receive 487, Request Terminated, from the callee. For no
answer, the timer will expire and ser generate a 408, Request Timeout.
RFC2543 needed to define return code 487 as NOANSWER
and a
new code 488 as HUNGUP
RFC2543 is obsoleted by RFC3261. As explained above, the timer will expire
when no answer. There is no need to add new code here. Besides, how can one
determine no answer other than checking for timeout?
Zeus
7155
days inactive
7156
days old
1 comments
2 participants
participants (2)
-
Java Rockx -
Zeus Ng