search for: da93e2ee

Displaying 3 results from an estimated 3 matches for "da93e2ee".

2015 Jan 20
2
Problem with Cisco Phones
...nference mixing, which I guess it would do in CallManager? <--- SIP read from TCP:xxx.xxx.xxx.xxx:50604 ---> REFER sip:xxx.xxx.xxx.xxx SIP/2.0 Via: SIP/2.0/TCP xxx.xxx.xxx.xxx:50604;branch=z9hG4bK48c7492c From: "4005" <sip:4005 at xxx.xxx.xxx.xxx>;tag=203a07fceb4b00eff1377deb-da93e2ee To: <sip:4004 at xxx.xxx.xxx.xxx> Call-ID: OutOfDialog--001e-67a906f5-5333c2b8 at xxx.xxx.xxx.xxx Max-Forwards: 70 Date: Tue, 20 Jan 2015 17:10:19 GMT CSeq: 101 REFER User-Agent: Cisco-CP7945G/9.4.2 Contact: <sip:4005 at xxx.xxx.xxx.xxx:50604;transport=tcp> Referred-By: "4005"...
2015 Jan 20
0
Problem with Cisco Phones
...it would do in CallManager? > > <--- SIP read from TCP:xxx.xxx.xxx.xxx:50604 ---> > REFER sip:xxx.xxx.xxx.xxx SIP/2.0 > Via: SIP/2.0/TCP xxx.xxx.xxx.xxx:50604;branch=z9hG4bK48c7492c > From: "4005" <sip:4005 at xxx.xxx.xxx.xxx > >;tag=203a07fceb4b00eff1377deb-da93e2ee > To: <sip:4004 at xxx.xxx.xxx.xxx> > Call-ID: OutOfDialog--001e-67a906f5-5333c2b8 at xxx.xxx.xxx.xxx > Max-Forwards: 70 > Date: Tue, 20 Jan 2015 17:10:19 GMT > CSeq: 101 REFER > User-Agent: Cisco-CP7945G/9.4.2 > Contact: <sip:4005 at xxx.xxx.xxx.xxx:50604;transport=tc...
2015 Jan 20
2
Problem with Cisco Phones
We were using G722 - I thought similarly and tried a call with alaw. Same problem occurred, any other ideas? > I'm willing to bet you are forcing the use of G729. 7940 and 7960 phones can > only do a single G729 channel, and if you require G729 for the second leg of a > conference, it will fail. This message may be private and confidential. If you have received this message in