[SFtrack] Commented: (XECS-1591) Paging server mishandles page to a user with multiple phones
[
http://track.sipfoundry.org/browse/XECS-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_30408
]
Scott Lawrence commented on XECS-1591:
--------------------------------------
The example of a home and office phone is an extreme one, but we don't need it
to show that this is a problem.
Simpler and more common examples are shared lines, or lines that are assigned
to a primary phone and to a backup.
> Paging server mishandles page to a user with multiple phones
> ------------------------------------------------------------
>
> Key: XECS-1591
> URL: http://track.sipfoundry.org/browse/XECS-1591
> Project: sipXecs
> Issue Type: Bug
> Components: sipXpage
> Affects Versions: 3.10.1
> Environment: [root@scsalpha sipxpbx]# sipx-config --version
> sipX version information:
> sipxportlib 3.10.1-012233 2008-04-14T18:08:20 oem-centos5
> sipxtacklib 3.10.1-012233 2008-04-14T18:13:36 oem-centos5
> sipxmedialib 3.10.1-012233 2008-04-14T18:17:34 oem-centos5
> sipxcalllib 3.10.1-012233 2008-04-14T18:21:26 oem-centos5
> sipxcommserverlib 3.10.1-012233 2008-04-14T18:26:07 oem-centos5
> sipxregistry 3.10.1-012233 2008-04-14T18:30:52 oem-centos5
> sipxpublisher 3.10.1-012233 2008-04-14T18:30:15 oem-centos5
> sipxproxy 3.10.1-012233 2008-04-14T18:29:15 oem-centos5
> sipxconfig 3.10.1-012233 2008-04-14T18:39:49 oem-centos5
> sipxvxml 3.10.1-012233 2008-04-14T18:32:36 oem-centos5
> sipxacd 3.10.1-012233 2008-04-14T18:42:50 oem-centos5
> sipxpbx 3.10.1-012233 2008-04-14T18:45:06 oem-centos5
> Reporter: Mark Gertsvolf
> Priority: Critical
> Fix For: 4.0
>
> Attachments: sipx-configuration-scsalpha.ca.nortel.com.tar.gz
>
>
> Paging server does not properly handle a case where a target user is
> registered from multiple phones.
> First the expectation of a user registered from two sets is that both phones
> get a page. I have one phone in my office and another set in my home office.
> I expect a page to reach me at both places.
> Perhaps this behavior is a candidate for a separate enhancement ticket.
> On top of that in the case of multiple phones paging server also leaves some
> phones with a phantom stranded call. This is a result of a common condition,
> when multiple phones answer the page at the same time. Paging server does not
> properly handle multiple 200OK responses.
> Paging server receives 200OK from phoneA and ACKs it. When the second 200OK
> arrives from phoneB paging server does not ACK the call but replaces the
> dialog remote target with the data from the second call. At the end of the
> page the BYE is sent to the phoneB and the call at phoneA is left stranded.
> In the attached logs: original paging call:
> 94c10f08-2f87a24e-13c4-19a3c-be746a1-19a3c@xxxxxxxxxxxxxxxxxxxxxx
> Problematic outgoing call: 6d78b1215b45cb5cff803fcc2b6be235@xxxxxxxxxxxxx
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://track.sipfoundry.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
