Hoping someone might be able to shed some light on this (otherwise it will at least make the issue known because I didn’t get any similar sightings googling).
For some reason I’m unable to set up a local conference call on a Cisco 7945 and 8961. (using the phones internal bridge that is). The phones will nicely announce on screen they couldn’t set up the conference when trying to do so.
Versions used;
Asterisk 1.6.2.12 + Cisco 7945 fw 9.0.3
Asterisk 1.6.2.14 + Cisco 8961 fw 9.0.0.77
I’m using TCP transport in both setups. I’ve tried insecure port and invite and allow reinvites, but to no avail.
I’m having no issues in another environment running Asterisk 1.4.22 + Cisco 7945 fw 8.5.2 in udp.
I know I should be able to change the transport to udp in the config files of the phones. I’ll try that as soon as I have some time.
Maybe Cisco altered the way they do this from fw v9.x on.
It sure would be nice to retain this feature for users with the current releases.
Below the SIP REFER request from the 8961 that I believe should set up the conference and is declined by lack of a dialog by Asterisk. I have no reference yet to the SIP messaging in a working old setup, but I’ll try to obtain that information when I can.
To: <sip:192.168.1.152>^M
Call-ID: [email protected]^M
Date: Thu, 30 Dec 2010 07:00:35 GMT^M
CSeq: 1903 REFER^M
User-Agent: Cisco-CP8961/9.0.1^M
Accept: application/x-cisco-remotecc-response+xml^M
Expires: 60^M
Max-Forwards: 70^M
Contact: <sip:[email protected]:51904;transport=TCP>^M
Referred-By: "displayname" <sip:[email protected]>^M
Refer-To: cid:[email protected]^M
Content-Id: <[email protected]>^M
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE^M
Content-Length: 961^M
Content-Type: application/x-cisco-remotecc-request+xml^M
Content-Disposition: session;handling=required^M
^M
<?xml version="1.0" encoding="UTF-8"?> ^M
<x-cisco-remotecc-request>^M
<softkeyeventmsg>^M
<softkeyevent>Conference</softkeyevent>^M
<dialogid>^M
<callid>[email protected]</callid>^M
<localtag>1c17d340f023031a5327b63a-28afcf2d</localtag>^M
<remotetag>as628d1f70</remotetag>^M
</dialogid>^M
<linenumber>0</linenumber>^M
<participantnum>0</participantnum>^M
<consultdialogid>^M
<callid>[email protected]</callid>^M
<localtag>1c17d340f023031b72d1cafd-3f4ab164</localtag>^M
<remotetag>as2bd95e30</remotetag>^M
</consultdialogid>^M
<state>false</state>^M
<joindialogid>^M
<callid></callid>^M
<localtag></localtag>^M
<remotetag></remotetag>^M
</joindialogid>^M
<eventdata>^M
<invocationtype>explicit</invocationtype>^M
</eventdata>^M
<userdata></userdata>^M
<softkeyid>0</softkeyid>^M
<applicationid>0</applicationid>^M
</softkeyeventmsg>^M
</x-cisco-remotecc-request>^M
<------------->
[Dec 30 08:00:37] VERBOSE[8103] chan_sip.c: --- (19 headers 30 lines) ---
[Dec 30 08:00:37] VERBOSE[8103] chan_sip.c:
<--- Transmitting (NAT) to 192.168.1.199:51904 --->
SIP/2.0 603 Declined (no dialog)^M
Via: SIP/2.0/TCP 192.168.1.199:51904;branch=z9hG4bK53432641;received=192.168.1.199^M
From: "displayname" <sip:[email protected]>;t
Thanks,
Bas