Hi Scott, SIP logging on the Avaya is a little "complex", but I'll see what I can find.
I have however just seen this http://track.sipfoundry.org/browse/XX-5643 and wondered if it might be applicable. Cheers Arne On Mon, Oct 26, 2009 at 2:50 PM, Scott Lawrence <scott.lawre...@nortel.com> wrote: > On Mon, 2009-10-26 at 12:36 +0000, shouldbe q931 wrote: >> Hi Scott, >> >> I'm a little unsure of how to use a Token in the filter, so I just >> used "6" I'm also too much of a newbie to find the call-id for the >> failing calls :-( > > The easiest filter would probably be '6999' - the caller number you > used. For transfers, the call-id isn't all that good a choice, since > there's usually more than one. > >> As this is not yet in production, I'd be happy to clean/dump the >> existing logs, but I haven't found a method to do this on the wiki. > >> The Avaya is on 10.201.1.5 >> The sipXecs is on 10.200.100.33 >> >> I am calling from extension 6999 on the Avaya system. >> >> The Auto attendant is configured to be on 6815 from the dialplan. The >> 6810 extension and 6812 conference were manually configured. >> >> As this is public distribution, I've done some basic "cleaning" of the >> xml, swapping out the domain name, hostname and my surname etc. If >> this presents a problem I can email you the original xml. > > Best not to modify the data - there's nothing in these traces that's > security-sensitive (for example, unless you've manually simplified the > SIP passwords to make them easy to guess, a brute force attack on digest > authentication is hard), especially if you're really using private > addresses, but feel free to send directly to me. > > What you should be seeing is a REFER coming back from the auto-attendant > with a Refer-To header that has the conference address. I see one REFER > that might be that in your trace: > > REFER sip:10.201.1.5:5062;transport=tcp;x-sipX-nonat SIP/2.0 > Route: <sip:10.201.1.5:5062;lr;transport=tcp> > From: "6810" <sip:6...@domain.local>;tag=2066392356 > To: "Arne 6999, Surname-Hidden" > <sip:anonym...@anonymous.invalid:5062>;tag=0f2b15adc3de1ef5f4ac758b500 > Call-Id: 0f2b15adc3de1f05f4ac758b500 > Cseq: 2 REFER > Contact: > "6810"<sip:6...@10.200.100.33:5100;transport=tcp;voicexml=https%3A%2F%2F10.200.100.33%3A8091%2Fcgi-bin%2Fvoicemail%2Fmediaserver.cgi%3Faction%3Ddeposit%26mailbox%3D6810%26lang%3Den;x-sipX-nonat> > Referred-By: "6810"<sip:6...@domain.local> > Refer-To: > <sip:conflo...@domain.local?x-sipx-authidentity=%3csip%3a%7e%7eid%7emedia%40domain.local%3bsignature%3d4ae57a45%253a%253a5ab351d24589c5dfe4ff658ef502e606%3e> > > but what I should see shortly after that is an INVITE from the Avaya to > the address in the Refer-To header, but I don't see that. You might > want to look in the logs on the Avaya to see what it's doing with the > REFER. > > > > _______________________________________________ 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 sipXecs IP PBX -- http://www.sipfoundry.org/
