>Regardless of which ITSPs support it, it is a requirement of the >offer-answer model that re-invite with no SDP attribute return an >offer. This offer can be the same as the original offer but it is a >protocol error to return OK with no SDP body. > >Note (thanks to Dale for digging this out for me) : > >RFC 3261, section 13.2.1, especially: > Concretely, the above rules specify two exchanges for UAs compliant > to this specification alone - the offer is in the INVITE, and the > answer in the 2xx (and possibly in a 1xx as well, with the same > value), or the offer is in the 2xx, and the answer is in the ACK. > All user agents that support INVITE MUST support these two exchanges. > >I have to say it is not a valid argument to state that it is OK to >make this error because Verizon "and other DID providers" do. > >I have some code to try to compensate for this particular error. It >has not been my priority to make this hack work. If you wish you can >supply your SIP credentials and I can try to get it to work on 4.1 as >time permits. > >Regards, > >Ranga.
Thanks Ranga, I will pass your comments to Bandtel. We have decided to move the customer from Bandtel, we used them alot in the past but have been less than happy for the last few implementations. Typically we use ingate devices but with 4.x release we are now using sipxbridge for our more budget aware customers. Bandwidth.com does not service are area...do you have any thoughts on Voxitas or other trunk provider that you have good consistent results with sipxbridge? -M _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
