Topic: Selintra Extensions - Strange Problem

[gippsweb]

I've been running SAIL very successfully for over 6 months now, except for one strange problem that seems to have crept in during an upgrade which I had to rollback (I think).

I have a remote extension (at home) which can be called from any other extension using it's extension number. The problem shows up when this extension makes a call, it shows up as a totally different extension number.

I've checked the cid info for the extension involved, even deleted it and recreated it, it still shows the other damn number.
All the cid info at the remote end is correct as the other phone there works fine. I even swapped the two remote ones around with no difference.

Does anyone have any ideas? I'm almost tempted to change the extension to match the dud info it brings up for an easy way out.

[SARK devs]

Hi Mate,

Interesting problem.  It would drive me round the bend.  

CID, as you know, is generated as part of the sip control sequences being sent from the phone.  

Areas to look first.  Check sip.conf to see if the rogue CID appears anywhere.  While you're at it do a search on the selintra database with

cat /home/e-smith/db/selintra | grep nnnn

substitute the rogue extension number for nnnn.

If that doesn't show the rogue CID then it is almost certainly coming off the phone itself.  You can prove this by watching the SIP invite stream during call set-up.   You'll need ethereal...

Install ethereal with

Code: [Select]

yum install ethereal --enablerepo=base

Then run

Code: [Select]

tethereal -i ethn host nnn.nnn.nnn.nnn

substitute the phone's address for nnn...

If the phone is remote then you should watch eth1.  if the phone is local, you should watch eth0.

Stop ethereal with ^C

For a detailed view of the SIP packets run...

Code: [Select]

tethereal -Vi ethn host nnn.nnn.nnn.nnn

This should show you what's in the invite and what CID's are flying around.



Kind Regards

Selintra