<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Well, this is the way it should be. From SER's perspective, there is an
early dialog going on with SEMS that is likely to result in a dialog
and it should NOT cancel. I'm sure there is an RFC that describes this
call scenario, I seem to remember reading something, but I don't
remember good enough the scenario to try to describe it here. However,
I don't know which one :-) You probably don't get into failure route
either, because all the branches haven't failed yet, so you are
definitely on the wrong track. <br>
<br>
Would be nice if you post the solution in a how-to at <a class="moz-txt-link-freetext" href="http://iptel.org/">http://iptel.org/</a>
when you figure it out!<br>
g-)<br>
<br>
<br>
<br>
<br>
Vamsi Pottangi wrote:
<blockquote
cite="midcd10de770609061101i2a0f5d25q27855a7cf4fabe11@mail.gmail.com"
type="cite">Hi,<br>
<br>
In my test setup, I have SER as proxy and SEMS as announcement server.
In SER config I'm sending forking invite to SEMS using append_branch
for every call made. For example when User1 dials User2, SER send
INVITES to both SEMS and User2, while the User2 phone rings,
announcement is played from SEMS to User1 using the early media 183
session progress message. Once the User2 answers the call, a CANCEL
message is sent to SEMS and normal conversation happens between User1
and User2 which is expected.
<br>
<br>
The problem which I'm facing is that when User2 doesn't answer the call
or if rejects the call, SER never sends CANCEL to SEMS, so the
annoucement is being played continously to User1 and User1 is unaware
of the remote party status. How can I configure the SER script to
handle such unanswered or call reject cases and send CANCEL to SEMS and
inform User1 about the unanswered or cancel status?
<br>
<br>
Does it cancel 183 progress only in case of 200 OK from other invite
session? how can we handle others like 408, 486 etc?<br>
<br>
I'm not pasting my ser.cfg here because it is the basic sample script
with just append_branch("SEMS") in case of INVITE.
<br>
<br>
Did anybody tried out such scenarios? Any help would be appreciated.<br>
<br>
Thanks,<br>
~Vamsi<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Serusers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a>
<a class="moz-txt-link-freetext" href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a>
</pre>
</blockquote>
</body>
</html>