I swear, it used to work.
I have not upgraded since. running 4.2.0, cisco FW 8-13, poly 650,
3.13c, poly 335, 3.2.1.
I went back to DEFAULT phone groups on the cisco and poly.
remote calls are fine, doesn't matter who puts who on hold. local holds
seem broken now.
if a cisco phone puts another local cisco phone on hold, and takes them
off, fine.
if a poly puts a poly on hold, and takes them off fine.
if a poly puts a cisco on hold and takes them off, fine.
*if a cisco puts a poly on hold, and takes them off, I get disconnected.*
I tried this in SIPDefault, setting to 0 or 1, didn't make any difference:
# rfc_2543 is OBSOLETE, c=0.0.0.0 hold is OBSOLETE, poly's use
a=sendonly, rfc_3264
# supposedly, all cisco phones from fw 7-5 on use 3264.
rfc_2543_hold: 0
2010-08-13 16:39:54.303120 10.72.0.243 -> 10.72.0.2 SIP/SDP Request:
INVITE sip:1...@10.72.0.254;sipXecs-CallDest=INT, with session description
2010-08-13 16:39:54.304600 10.72.0.2 -> 10.72.0.243 SIP Status: 100
Trying
2010-08-13 16:39:54.309935 10.72.0.2 -> 10.72.0.254 SIP/SDP Request:
INVITE sip:1...@10.72.0.254, with session description
A polycom and a cisco phone go into a bar and order a hold..
The cisco says to the bartender: SIP/SDP Request: INVITE
sip:1...@10.72.0.254;sipXecs-CallDest=INT, with session description
Bartender say to the cisco: SIP Status: 100 Trying
then the bartender says to the polycom: SIP/SDP Request: INVITE
sip:1...@10.72.0.254, with session description
ready for the punch line?
the polycom says back to the bartender 2010-08-13 16:39:54.326884
10.72.0.254 -> 10.72.0.2 SIP Status: 400 Bad Request
apparently, here is the offensive joke that the cisco told to the
bartender and asked him to pass along to the polycom:
Session Initiation Protocol
Request-Line: INVITE sip:1...@10.72.0.254 SIP/2.0
Method: INVITE
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP
10.72.0.2;branch=z9hG4bK-XX-6e10of0y4PUcUEoQj`C2ZEoxvA
Transport: UDP
Sent-by Address: 10.72.0.2
Branch: z9hG4bK-XX-6e10of0y4PUcUEoQj`C2ZEoxvA
Via: SIP/2.0/UDP 10.72.0.243:5060;branch=z9hG4bK34c2eb86
Transport: UDP
Sent-by Address: 10.72.0.243
Sent-by port: 5060
Branch: z9hG4bK34c2eb86
From:
<sip:1...@secnap.com;user=phone>;tag=000750d54eba000a5b917c33-3fc2612a
SIP from address: sip:1...@secnap.com
SIP tag: 000750d54eba000a5b917c33-3fc2612a
To: "Michael Scheidell" <sip:1...@secnap.com>;tag=73987285-C80F6772
SIP Display info: "Michael Scheidell"
SIP to address: sip:1...@secnap.com
SIP tag: 73987285-C80F6772
Call-Id: c005c616-617bf707-594a4...@10.72.0.254
Max-Forwards: 20
Cseq: 101 INVITE
Sequence Number: 101
Method: INVITE
User-Agent: Cisco-CP7960G/8.0
Contact: <sip:1...@10.72.0.243:5060;transport=udp;x-sipX-nonat>
Contact Binding:
<sip:1...@10.72.0.243:5060;transport=udp;x-sipX-nonat>
URI: <sip:1...@10.72.0.243:5060;transport=udp;x-sipX-nonat>
SIP contact address: sip:1...@10.72.0.243:5060
Accept: application/sdp
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE
Supported: replaces,join,norefersub
Content-Length: 270
Content-Type: application/sdp
Content-Disposition: session;handling=optional
Date: Fri, 13 Aug 2010 20:37:07 GMT
Record-Route: <sip:;sipXecs-CallDest=INT>
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): Cisco-SIPUA 20633 1 IN IP4
10.72.0.243
Owner Username: Cisco-SIPUA
Session ID: 20633
Session Version: 1
Owner Network Type: IN
Owner Address Type: IP4
Owner Address: 10.72.0.243
Session Name (s): SIP Call
Time Description, active time (t): 0 0
Session Start Time: 0
Session Stop Time: 0
Media Description, name and address (m): audio 24844
RTP/AVP 0 8 18 101
Media Type: audio
Media Port: 24844
Media Proto: RTP/AVP
Media Format: ITU-T G.711 PCMU
Media Format: ITU-T G.711 PCMA
Media Format: ITU-T G.729
Media Format: 101
Connection Information (c): IN IP4 0.0.0.0
Connection Network Type: IN
Connection Address Type: IP4
Connection Address: 0.0.0.0
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute Fieldname: rtpmap
Media Attribute Fieldname: rtpmap
Media Format: 18
MIME Type: G729
Media Attribute (a): fmtp:18 annexb=no
Media Attribute Fieldname: fmtp
Media Format: 18 [G729]
Media format specific parameters: annexb=no
Media Attribute (a): rtpmap:101 telephone-event/8000
Media Attribute Fieldname: rtpmap
Media Format: 101
MIME Type: telephone-event
Media Attribute (a): fmtp:101 0-15
Media Attribute Fieldname: fmtp
Media Format: 101 [telephone-event]
Media format specific parameters: 0-15
Media Attribute (a): inactive
the polycom got so upset, he said this:
Session Initiation Protocol
Status-Line: SIP/2.0 400 Bad Request
Status-Code: 400
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP
10.72.0.2;branch=z9hG4bK-XX-6e10of0y4PUcUEoQj`C2ZEoxvA
Transport: UDP
Sent-by Address: 10.72.0.2
Branch: z9hG4bK-XX-6e10of0y4PUcUEoQj`C2ZEoxvA
Via: SIP/2.0/UDP 10.72.0.243:5060;branch=z9hG4bK34c2eb86
Transport: UDP
Sent-by Address: 10.72.0.243
Sent-by port: 5060
Branch: z9hG4bK34c2eb86
From:
<sip:1...@secnap.com;user=phone>;tag=000750d54eba000a5b917c33-3fc2612a
SIP from address: sip:1...@secnap.com
SIP tag: 000750d54eba000a5b917c33-3fc2612a
To: "Michael Scheidell" <sip:1...@secnap.com>;tag=73987285-C80F6772
SIP Display info: "Michael Scheidell"
SIP to address: sip:1...@secnap.com
SIP tag: 73987285-C80F6772
CSeq: 101 INVITE
Sequence Number: 101
Method: INVITE
Call-ID: c005c616-617bf707-594a4...@10.72.0.254
Record-Route:
User-Agent: PolycomSoundPointIP-SPIP_650-UA/3.1.3.0439
Accept-Language: en
Content-Length: 0
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
ISN: 1259*1300
> *| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot Company Award Winner, World Executive Alliance
* Five-Star Partner Program 2009, VARBusiness
* Best in Email Security,2010: Network Products Guide
* King of Spam Filters, SC Magazine 2008
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
