Caller ID mapping to System Directory

rob · ‎03-08-2012

So far the UC320 is working well and replacing an existing Panasonic TD816 system for my customer.

Caller ID is being presented on the phones when an external call is received - however in the previous system, the Caller ID would be matched to the System Directory and if present, the name of the caller (from the directory entry) would be displayed instead.

This made it easier for the users to know who was calling without having to memorise lots of numbers!

This seems to be a relatively standard feature on all small business PBX systems - have I just missed how to implement this in the GUI or is it a feature request that could be added to the roadmap?

Thanks,

Rob.

Alberto Montilla · ‎03-08-2012

Hi Rob;

Thanks for your email. Glad to hear your deployment is going well.

We have detected the caller ID match to directory is too strict, so match is not happening probably since the string coming does not match exactly to the number. We have this enhancement on the next for the next major release 2.3, which is planned (though not committed yet) for summer 2012. Please stay tuned.

Regards;
Alberto

rob · ‎03-08-2012

Hi Alberto,

Is there any more detail on what it's matching? The users don't realy use the system directory for making calls, so I have the option to change the numbers in the directory to exactly match what's required for them to match up.

For example - in the Syslog for an incoming SIP call I have:

----

From: "07775715715" <>07775715715@sipgate.co.uk>;tag=as72458bba

To: <>00441183215369@sipgate.co.uk>

Contact: <07775715715>

----

And in the system directory I have an entry for 07775715715 which doesn't make the match at the moment.

Is there someway to see in the syslog what the actual number needs to be in the directory to force the match until the 2.3 release is out?

Thanks,

Rob.

Alberto Montilla · ‎03-08-2012

Hi Rob;

Can you send me the whole SIP INVITE message and also let me know what number the phone is showing on the screen as caller ID.

Regards
Alberto

rob · ‎03-08-2012

Hi Alberto,

The phone is showing 07775715715 as callerid on the display - INVITE is below:

Thanks,

Rob.

-----

Mar 8 12:46:37 UC320W user.debug voice: INVITE sip:1479886@86.21.113.230:5071 SIP/2.0

Record-Route: <217.10.79.23>

Record-Route: <172.20.40.1>

Record-Route: <217.10.79.23>

Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bKe42.7a42af71.0

Via: SIP/2.0/UDP 172.20.40.1;branch=z9hG4bKe42.7a42af71.0

Via: SIP/2.0/UDP 217.10.79.23:5060;received=217.10.68.222;branch=z9hG4bK6cf58628

Via: SIP/2.0/UDP 217.116.117.5:5060;received=217.116.117.5;branch=z9hG4bK6cf58628;rport=5060

Max-Forwards: 67

From: "07775715715" <>07775715715@sipgate.co.uk>;tag=as72458bba

To: <>00441183215369@sipgate.co.uk>

Contact: <07775715715>

Call-ID: 590dca256927546555c53c0c15446d02@sipgate.co.uk

CSeq: 102 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO

Supported: replaces, timer

Content-Type: application/sdp

Content-Length: 430

v=0

o=root 2124718516 2124718516 IN IP4 217.116.117.5

s=sipgate VoIP GW

c=IN IP4 217.116.117.5

t=0 0

m=audio 19854 RTP/AVP 8 0 3 97 18 112 101

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:3 GSM/8000

a=rtpmap:97 iLBC/8000

a=fmtp:97 mode=30

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:112 G726-32/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=silenceSupp:off - - - -

a=ptime:20

a=sendrecv

-----

Alberto Montilla · ‎03-12-2012

Dear Rob;

I have escalated your case to engineering as it seems this issue is beyond the strict matching I was talking about. Stay tuned.

Regards;
Alberto

juliomar · ‎03-12-2012

Hi Rob,

We have identified that this feature is currently broken, and we have opened a couple of defects to track this issue. SPA 50x, SPA30x - CSCty59185, and for the SPA525 we have defect CSCty59171.

The incoming sip call should match your personal directory entry name if the caller phone number matches your entry.

Best regards,

Julio

rob · ‎03-12-2012

Thanks for the update Julio - I presume this gets added to the fix list for a future release, or is there a specific patch that will be created?

Kind Regards,

Rob.

juliomar · ‎03-12-2012

Hi Rob,

I believe the fix will be incorporated to a near future Limited Deployment/General release as this should have high priority.

Cheers,

Julio

g.chierici · ‎03-20-2012

HI Julio,

Firmware release 2.2.2 seems doesn't solve this issue.

Do you have any news about it ?

Thanks

juliomar · ‎03-20-2012

Hi Giorgio,

The bug has been already identified as resolved by development team. However, since this fix has not made it to an official phone firmware release, it was not available for the UC320W 2.2.2 release. A near future firmware release with newer phone loads may have this fix in.

Cheers,

Julio

g.chierici · ‎04-24-2012

Hi Julio,

Are there any news about this issue ?

It seems impossible that you have not released a patch for this...

Thanks

Giorgio

g.chierici · ‎06-15-2012

Hi Cisco Team,

Seems like Firmware release 2.2.3(5) don't fix this issue.

Since the development team has already resolved the bug, why you don't make available a patch ?

Hope we don't have to wait until fall with the release 2.3...

Thanks

Giorgio