Hi all,
My callweaver installation is (sometimes) generating corrupt SDP packets
on invite when chan Local is involved in the communicatio process.
Here is a dialplan example which i use to reproduce the problem:
[default]
exten => _X.,1,Dial(Local/[EMAIL PROTECTED]&Local/[EMAIL PROTECTED])
[test]
exten => _1X.,1,Wait(20)
exten => _1X.,n,Dial(Local/${EXTEN:[EMAIL PROTECTED],20,tT)
exten => _2X.,1,Dial(Local/${EXTEN:[EMAIL PROTECTED],20,tT)
[phones]
exten => _X.,1,Dial(Local/${EXTEN:[EMAIL PROTECTED],20,tT)
[local]
exten => 13,1,Dial(SIP/13,20,tT)
exten => 14,1,Dial(SIP/14,20,tT)
A new call goes into context default, where it get split into 2 call
legs, one of which get executed immediately and the other one is delayed
20 seconds.
The invite packet that get sent to the extension which ring immediately
is often corrupt:
INVITE sip:[EMAIL PROTECTED]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.3:5060;branch=z9hG4bK4dccb6fb;rport
From: "callweaver" <sip:[EMAIL PROTECTED]>;tag=as18090017
To: <sip:[EMAIL PROTECTED]:5060>
Contact: <sip:[EMAIL PROTECTED]>
Call-ID: [EMAIL PROTECTED]
CSeq: 102 INVITE
User-Agent: Pbx
Max-Forwards: 70
Date: Thu, 25 Sep 2008 10:45:05 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 332
v=0
o=root 2744 2744 IN IP4 192.168.3.3
s=session
c=IN IP4 192.168.3.3
t=0 0
m=audio 11744 RTP/AVP 0 3 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:34 H263/90000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
m=video 11748 RTP/AVP 34
å͵øOÆ·ÕÔ͵HÙ͵
Notice those strange chars in the last line... well they are not
supposed to be there.
I tried to tcpdump the call and the wrong chars are also sent to the
net, not just printed in the cli and they seem to be the cause for which
some phones send rtp traffic to 0.0.0.0 instead of 192.168.3.3 (pbx
address).
Can anyone successfully replicate the problem on his installation?
I also noticed that more "Local steps" are involved in the call, higher
is the chance to get a corrupt sdp packet.
Regars,
Enrico
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
