|Summary:||ASTERISK-07755: [patch] Caller ID blocking fails: RPID settings from extension not carried to trunk|
|Date Opened:||2006-09-17 11:03:42||Date Closed:||2006-10-26 15:08:33|
|Environment:||Attachments:||( 0) rpid.patch|
|Description:||When the extension invites a call and presents RPID as:|
Remote-Party-ID: Ed Greenberg <sip:email@example.com>;screen=yes;privacy=full;party=calling
and Asterisk dials as
Sep 17 15:47:55 VERBOSE logger.c: -- Executing Dial("SIP/299-09844708", "SIP/xo/408xxxyyyy|120|") in new stack
Asterisk presents RPID to the trunk as:
Remote-Party-ID: "Ed Greenberg" <sip:firstname.lastname@example.org>;privacy=off;screen=no
This causes caller ID blocking to fail.
****** ADDITIONAL INFORMATION ******
I am using a Sipura 2000 on the extension end... connecting to XO. (Trying to pass XO interoperability testing) I'm dialing *67 and creating a proper RPID header, but Asterisk seems to be losing these settings.
I have full packet captures available upon request to developers. If needed, I'll sanitize and post them.
|Comments:||By: Joshua C. Colp (jcolp) 2006-09-17 16:50:42|
Do you have trustrpid set to yes in sip.conf? If not then RPID will not be used. As well it may not be exactly transmitted as received.
By: edgreenberg (edgreenberg) 2006-09-17 17:25:33
Right at the top:
By: edgreenberg (edgreenberg) 2006-09-18 12:37:01
This seems fixed in the SVN trunk r43075. I'm rerunning my tests. I'd love some help in figuring out what change fixed this and if it can be installed as a patch to 184.108.40.206.
By: Olle Johansson (oej) 2006-09-18 15:00:34
Please check callingpres values during the call with dumpchan() or similar
By: edgreenberg (edgreenberg) 2006-09-18 16:15:06
CallingPres does not seem to appear in dumpchan() in either 220.127.116.11 nor in the SVN version.
Dumping Info For Channel: SIP/299-0819aae0:
CallerIDName= Ed Greenberg
State= Ring (4)
Blocking_in= (Not Blocking)
CALLERID="Ed Greenberg" <408xxxxxxx>
By: edgreenberg (edgreenberg) 2006-09-24 18:19:59
I found that bug 7240, which was fixed in the trunk, would resolve this problem. I backported it to 18.104.22.168 (patch attached) and I am able to carry rpid through now.
By: Olle Johansson (oej) 2006-10-26 15:08:33
Thanks for the reminder. Finally fixed in 1.2 too.