[asterisk-bugs] [Asterisk 0018367]: Missing P-Asserted-Identity
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Apr 14 16:58:12 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18367
======================================================================
Reported By: GeorgeKonopacki
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18367
Category:
Channels/chan_sip/CallCompletionSupplementaryServices
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
Asterisk Version: 1.8.0
JIRA: SWP-2649
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-11-24 07:19 CST
Last Modified: 2011-04-14 16:58 CDT
======================================================================
Summary: Missing P-Asserted-Identity
Description:
Phone A is monitoring Phone B.
Phone B becomes available so the Asterisk server sends a NOTIFY(cc-ready)
to Phone A.
Phone A calls Phone B (using the URI provided by the NOTIFY(cc-ready)).
Phone B receives P-Asserted-Identity in its INVITE message – GOOD
Phone A does NOT receive P-Asserted-Identity in any of its messages –
BAD
This means the Phone A is displaying the 32 digit URI. Phone B displays
the information provided by the P-Asserted-Identity.
SIP.CONF
sendrpid = yes
sendrpid = pai
======================================================================
----------------------------------------------------------------------
(0133790) mmichelson (administrator) - 2011-04-14 16:58
https://issues.asterisk.org/view.php?id=18367#c133790
----------------------------------------------------------------------
I've uploaded some configs that I tested that allowed for correct connected
line information to be displayed.
To explain a bit, I initially did not have those CONNECTEDLINE(any)
function calls in the dialplan. When I ran my test, correct
P-Asserted-Identity information only came in the 200 OK. Then I added the
CONNECTEDLINE(any) function call prior to the Dial, and correct
P-Asserted-Identity information arrived in the 180 Ringing and the 200 OK.
I'm not 100% sure why info did not arrive in the 180 prior to the addition
of the CONNECTEDLINE(any) functions, because I think that simply setting
the callerid for the SIP peers and setting sendrpid=pai should have been
enough. But what I have here worked for me, so give it a try.
Issue History
Date Modified Username Field Change
======================================================================
2011-04-14 16:58 mmichelson Note Added: 0133790
======================================================================
More information about the asterisk-bugs
mailing list