[Home]

Summary:ASTERISK-07755: [patch] Caller ID blocking fails: RPID settings from extension not carried to trunk
Reporter:edgreenberg (edgreenberg)Labels:
Date Opened:2006-09-17 11:03:42Date Closed:2006-10-26 15:08:33
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) rpid.patch
Description:When the extension invites a call and presents RPID as:
Remote-Party-ID: Ed Greenberg <sip:299@fr02.xxx.net>;screen=yes;privacy=full;party=calling

and Asterisk dials as
Sep 17 15:47:55 VERBOSE[7904] 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:299@67.xxx.yyy.zzz>;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:

[general]
trustrpid=yes
sendrpid=yes
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 1.2.12.1.
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 1.2.12.1 nor in the SVN version.

Dumping Info For Channel: SIP/299-0819aae0:
================================================================================
Info:
Name=               SIP/299-0819aae0
Type=               SIP
UniqueID=           1158613994.0
CallerID=           299
CallerIDName=       Ed Greenberg
DNIDDigits=         1408xxxxxxx
State=              Ring (4)
Rings=              0
NativeFormat=       4
WriteFormat=        4
ReadFormat=         4
1stFileDescriptor=  8
Framesin=           0
Framesout=          0
TimetoHangup=       0
ElapsedTime=        0h0m0s
Context=            299
Extension=          1408xxxxxxx
Priority=           3
CallGroup=          
PickupGroup=        
Application=        DumpChan
Data=               verbose
Blocking_in=        (Not Blocking)

Variables:
CALLERID="Ed Greenberg" <408xxxxxxx>
SIPCALLID=8080dd69-b0b3419f@localhost
SIPUSERAGENT=Sipura/SPA3000-2.0.10(GWf)
SIPDOMAIN=192.168.1.110
SIPURI=sip:299@192.168.1.17:5060
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 1.2.12.1 (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.