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.
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.
tshark -t ad -r '$tracefile' -R 'sip.Call-ID contains $callID' -w - |
ngrep -I - -W byline -t
On 16/01/14 14:57, Tiago Geada wrote:
Second thought, that would only allow me to know if there is a problem
on asterisk or softphone.
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.
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..
even so, I will try and measure the impact on performance, however if
asterisk did send the wrong string, how could I debug that??
On 16 January 2014 14:27, Tiago Geada <tiago.ge...@gmail.com
<mailto:tiago.ge...@gmail.com>> wrote:
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
On 16 January 2014 14:09, Gareth Blades
<mailinglist+aster...@dns99.co.uk
<mailto:mailinglist+aster...@dns99.co.uk>> wrote:
On 16/01/14 10:47, Tiago Geada wrote:
Hi folks,
We've been having a weird issue... It is happening more often
in the last few months...
Most inbound calls, we have in our dialplan before Queue():
Set(CALLERID(name)=${PARTNER}:0:${CALLERID(num)}:${UNIQUEID}:${CHANNEL});
So when the call rings a member, softphone will show this
string ....
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!!
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!!
I searched full log, and Set() sets the correct string... I
can't figure why softphone shows a string from a past call !!
:(
Any hints ?
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.
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by
http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every
Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
