As Scott said, in general, you shouldn't copy trace information into the body of your e-mail, as it rarely survives transit. You should put the information into a file and attach it. However, in this case, you were your information didn't get mutilated.
On Tue, 2009-05-05 at 18:28 -0700, Mark Wood wrote: > 192.168.254.102 = Asterisk > 192.168.254.120 = SipXecs > > Call was initiated from the asterisk box X201 dialing the SipXecs extension > 2010 > > 192.168.254.102 192.168.254.120 > | | > 1: |U------------INVITE----------->| > 2: |<------100 Trying/INVITE------U| > 3: |<-----404 Not Found/INVITE----U| > 4: |U-------------ACK------------->| > > Generated SIP Workbench by BreakPoint Software, Inc. (www.sipworkbench.com) > > > <<<<< Msg #1 / Packet #36: 192.168.254.102:5060 --> 192.168.254.120:5060 >>>>> > INVITE sip:2...@192.168.254.120 SIP/2.0 > Via: SIP/2.0/UDP 192.168.254.102:5060;branch=z9hG4bK73879b9d;rport > From: "Mark Wood" <sip:2...@192.168.254.102>;tag=as16de1754 > To: <sip:2...@192.168.254.120> > Contact: <sip:2...@192.168.254.102> > Call-ID: 546261573c578496015ad7bb1742f...@192.168.254.102 > CSeq: 102 INVITE > User-Agent: Asterisk PBX > Max-Forwards: 70 > Date: Tue, 05 May 2009 23:54:42 GMT > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY > Supported: replaces > Content-Type: application/sdp > Content-Length: 268 I see that the request-URI is sip:2...@192.168.254.120. Although I think that the sipXecs host's IP address is supposed to be accepted as an alias, in general, it's best to use the sipXecs SIP domain name rather than the IP address. Dale _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
