It's allowed, though admittedly strange. None of the attributes for the second m= line have any significance.
Paul > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of > [email protected] > Sent: Wednesday, September 01, 2010 11:11 AM > To: [email protected] > Subject: [Sip-implementors] SDP with same transport type twice > > Hi > > I receive a re-INVITE for a switchover from G.711 to T.38 with the > following SDP: > > v=0 > o=ABC 1542876549 1542876550 IN IP4 W.X.Y.Z s=abs c=IN IP4 A.B.C.D > t=0 0 > m=image 32603 udptl t38 > a=T38FaxVersion:0 > a=T38MaxBitRate:9600 > a=T38FaxRateManagement:transferredTCF > a=T38FaxMaxBuffer:256 > a=T38FaxMaxDatagram:256 > a=T38FaxUdpEC:t38UDPRedundancy > m=image 0 UDPTL t38 > a=sendrecv > a=T38FaxVersion:0 > a=T38FaxRateManagement:transferredTCF > a=T38FaxMaxBuffer:0 > a=T38FaxMaxDatagram:512 > a=T38MaxBitRate:14400 > a=T38FaxUdpEC:t38UDPRedundancy > > Is this allowed by the standards? And if so, are the attributes for the > second/muted m line relevant, considering that the port was set to zero? > > Thank you > Fred > -- > GMX DSL SOMMER-SPECIAL: Surf & Phone Flat 16.000 für nur 19,99 > €/mtl.!* http://portal.gmx.net/de/go/dsl > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
