Mark,
We have also seen this behavior. In fact, we see a NOTIFY eventually being sent by the as5350 with a "200 OK" reported,
although in fact, the 5350 has made not attempt to INVITE the target in the Refer-To header. As far as I can tell, this is a bug
in the Cisco SIP implementation, and we are planning on opening a ticket to that effect.
Bruce
On Mar 31, 2005, at 12:39 AM, Mark Roeten wrote:
Dear Sirs,
Assume a connection between a sip endpoint and a POTS peer, AB connection. The access to the POTS is through a cisco gateway.
A (pots) ----------- AS5350 -------------- B sipEndpoint.
| | (Transfer the AB connection to AC) |
C sipEndpoint
Whenever we try to transfer the AB connection to AC, debug of the AS5350
shows the
the following messages:
Received:
REFER sip:[EMAIL PROTECTED]:5060 SIP/2.0
To: <sip:[EMAIL PROTECTED]>;tag=185DB8AC-1410
From: <sip:[EMAIL PROTECTED]>;tag=71775f65
Via: SIP/2.0/UDP 212.29.166.88;branch=z9hG4bKa85b.473d6683.0
Via: SIP/2.0/UDP
192.168.0.41:6360;received=212.29.160.129;branch=z9hG4bK-d87543 -497302518-1-
-d87543-;rport=6360
Call-ID: <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED]
CSeq: 3 REFER
Contact: <sip:[EMAIL PROTECTED]:6360>
Max-Forwards: 16
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE,
INFO
User-Agent: eyeBeam release 3004w stamp 16863
Refer-To: <sip:[EMAIL PROTECTED]>
Referred-By: 12345<sip:[EMAIL PROTECTED]>
Content-Length: 0
Sent:
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 212.29.166.88;branch=z9hG4bKa85b.473d6683.0,SIP/2.0/UDP
192.168.0.41:6360;received=212.29.160.129;branch=z9hG4bK-d87543 -497302518-1-
-d87543-;rport=6360
From: <sip:[EMAIL PROTECTED]>;tag=71775f65
To: <sip:[EMAIL PROTECTED]>;tag=185DB8AC-1410
Date: Wed, 30 Mar 2005 08:35:08 GMT
Call-ID: <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED]
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 3 REFER
Content-Length: 0
SipEndPoint B remains in de state "Requesting blind transfer". So the transfer is not established. Could you please help me out asap?
I am using Cisco IOS Software, 5350 Software (C5350-IS-M), Version 12.3(8)T3, RELEASE SOFTWARE (fc1).
dial-peer voice 1 pots application vxml voice-class aaa 1 incoming called-number 01079987 port 3/0:D !
dial-peer voice 2 pots application vxml voice-class aaa 1 incoming called-number 01079987 port 3/1:D !
dial-peer voice 3 voip application session destination-pattern 12345 voice-class aaa 1 session protocol sipv2 session target sip-server incoming called-number 12345 dtmf-relay sip-notify rtp-nte codec g711ulaw !
dial-peer voice 4 voip application session destination-pattern 06900 voice-class aaa 1 session protocol sipv2 session target sip-server dtmf-relay sip-notify rtp-nte codec g711ulaw !
dial-peer voice 5 pots destination-pattern 01876477 no digit-strip port 3/0:D !
sip-ua nat symmetric role passive nat symmetric check-media-src max-forwards 15 sip-server ipv4:212.29.166.88
Best regards,
Mark Roeten
TinTel B.V.
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
