<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
The SIP trace will give you an idea is perhaps something is becoming
corrupted. If you keep a log of the asterisk console output
(asterisk -rvvv) then you will see what it attempts to set the
callerid to and any errors.<br>
<br>
Another tip. When you have a look at the sip trace you will see the
call-id. If you make a note of this and run the following replacing
the call-id and the trace file with the appropriate values it will
display the sip trace in a very nice human readable format. tshark
comes with the wireshark pakage and ngrep is part of epel repository
if you are running centos.<br>
<br>
tshark -t ad -r '$tracefile' -R 'sip.Call-ID contains $callID' -w -
| ngrep -I - -W byline -t<br>
<br>
<br>
On 16/01/14 14:57, Tiago Geada wrote:
<blockquote
cite="mid:CAFmd8FhK4V0aBZwmkEpeTLUVX+9e-HGOcR6CYK+Wq4=EXcXFpg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:#000066">Second
thought, that would only allow me to know if there is a
problem on asterisk or softphone.</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:#000066">
<br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:#000066">Because
the old callerid(name) that was presented on the softphone,
belonged to a call made to a different peer, I doubt that it
would be a softphone problem.</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:#000066"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:#000066">Our
softphones are fixed with the same peer/extension .. if the
wrong callerid were originally called to the same peer.. I
guess that would be worth it..</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:#000066"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:#000066">even
so, I will try and measure the impact on performance, however
if asterisk did send the wrong string, how could I debug
that??</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 16 January 2014 14:27, Tiago Geada <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:tiago.geada@gmail.com" target="_blank">tiago.geada@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:#000066">You're
right, seems like a nice way to debug. Regarding that,
how would the impact be affected running it on asterisk
box? I guess only port 5060 is not too bad</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div>
<div class="h5">On 16 January 2014 14:09, Gareth
Blades <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:mailinglist+asterisk@dns99.co.uk"
target="_blank">mailinglist+asterisk@dns99.co.uk</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">
<div text="#000000" bgcolor="#FFFFFF">
<div>
<div> On 16/01/14 10:47, Tiago Geada wrote:
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,102)">Hi
folks,</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,102)">
<br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,102)">We've
been having a weird issue... It is
happening more often in the last few
months...</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,102)">
<br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,102)">Most
inbound calls, we have in our dialplan
before Queue():</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,102)">
<br>
</div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif">Set(CALLERID(name)=${PARTNER}:0:${CALLERID(num)}:${UNIQUEID}:${CHANNEL})</font><span
style="color:rgb(0,0,102);font-family:tahoma,sans-serif">;</span></div>
<div class="gmail_default"><span
style="color:rgb(0,0,102);font-family:tahoma,sans-serif"><br>
</span></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif">So when the call rings a
member, softphone will show this
string ....</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif"><br>
</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif">The issue is that
sometimes the string showing in the
softphone is not the same. Its a
string from a past call, in the
latest case I've seen, from about 40
days ago!!</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif"><br>
</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif">User took a screenshot,
I've searched for that uniqueid
showing in softphone in cdr, and
that string was valid for a
different call 40 days ago!!</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif"><br>
</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif"><br>
</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif">I searched full log, and
Set() sets the correct string... I
can't figure why softphone shows a
string from a past call !!</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif"><br>
</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif">:(</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif"><br>
</font></div>
<div class="gmail_default"><font
color="#000066" face="tahoma,
sans-serif">Any hints ?</font></div>
</div>
<br>
<fieldset></fieldset>
<br>
</blockquote>
</div>
</div>
I would leave tcpdump running capturing port
5060 so you can load it onto wireshark and have
a look at the sip headers. That will tell you if
the SIP is incorrect or if its a problem with
the client.<br>
</div>
<br>
</div>
</div>
<span class="HOEnZb"><font color="#888888">--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a
moz-do-not-send="true"
href="http://www.api-digital.com"
target="_blank">http://www.api-digital.com</a>
--<br>
New to Asterisk? Join us for a live introductory
webinar every Thurs:<br>
<a moz-do-not-send="true"
href="http://www.asterisk.org/hello"
target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a moz-do-not-send="true"
href="http://lists.digium.com/mailman/listinfo/asterisk-users"
target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</font></span></blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
</body>
</html>