I have installed Sametime C2C (server side) on a Domino 8.5.1 server and integrated this with CUCM 7.1.3. In the configuration file I have entered 7.1 for the CUCM version (It says enter 7 or higher to enable v7+ features). The policies in Sametime are allowing the users to see the 'call' button when they right click on their contacts. The trunk and everything is setup as per the installation document. We are not using digest authentication.
In the integrated Sametime/Notes client 8.5.1 we can enter the user's 'office' number in the preference ( have simply entered the 4 digit extension of my IP communicator here), when I go to sametime I can select this extension to dial out from. Now I cannot dial by right clicking on a user. Whatever number I try to dial, whether it be by right clicking on a user and selecting their call button or by typing a number in manually the call window pops up but nothing happens.
We can see the SIP messages coming from the Sametime server in a sniffer trace so CUCM is receiving the the SIP invite. The problem I think here is that the URI appears to be getting rejected by CUCM as it includes "tel:" which it cannot interpret.
Request-Line: REFER sip:tel:email@example.com;transport=tcp SIP/2.0 Method: REFER Request-URI: sip:tel:firstname.lastname@example.org;transport=tcp [Resent Packet: False] Message Header Via: SIP/2.0/TCP 10.1.0.77:5060;branch=z9hG4bKFL.CvHpp96wc0RdwuYKJGA~~19 Transport: TCP Sent-by Address: 10.1.0.77 Sent-by port: 5060 Branch: z9hG4bKFL.CvHpp96wc0RdwuYKJGA~~19 Max-Forwards: 70 To: <sip:tel:email@example.com> SIP to address: sip:tel:firstname.lastname@example.org SIP to address User Part: tel:7502 SIP to address Host Part: 10.1.1.1 From: <sip:tel:email@example.com>;tag=ds80295a8f SIP from address: sip:tel:firstname.lastname@example.org SIP from address User Part: tel:7502 SIP from address Host Part: 10.1.0.77 SIP tag: ds80295a8f Call-ID: 461e4f9c14a39c7d10Fa56843014f128e4c@10.1.0.77 CSeq: 101 REFER Content-Length: 0 Contact: <sip:tel:email@example.com;transport=tcp> Contact Binding: <sip:tel:firstname.lastname@example.org;transport=tcp> Refer-To: <sip:tel:email@example.com> Referred-By: "c2c" <sip:firstname.lastname@example.org>;x-cisco-monitor-call
Does anybody know why why are being sent this: sip:tel:email@example.com;transport=tcp SIP/2.0
I believe that the "tel" part of this request should not be sent by Sametime as next we see the message:
17838 218.512301 10.1.1.1 10.0.0.77 SIP Status: 416 Unsupported URI scheme
Could this be a configurable option not to send this part of the SIP message from Sametime? I don't think this is accepted as part of the SIP standards.
Perhaps I need to change the format of the users extension number in Sametime - but how?!!!
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...