Exchange Unified Messaging - SIP 302 Redirect = HELP

Hi All,

I have been trying to get asterisk 1.6.0.15 to work with Exchange Unified Messaging, seemingly a simple task since SIP TCP support has been added to Asterisk however for some reason I am not having much luck.

I actually have two issues outstanding but as they are seperate I have split them into seperate posts to avoind confusion.

This posts relates to my asterisk installation simply giving up after getting a SIP 302 from Exchange. I have read in through a number of issue logs and web guides indicating that this had been fixed several builds ago and asterisk would now follow up the 302 with a new INVITE using the information from the CONTACT header however in my case this is not happened.

My installation is a basic build on CentOS 5, asterisk 1.6.0.15. My test environment is as follows:

Exchange UM server: 192.168.37.22
Asterisk: 192.168.37.100

sip.conf

[general]
tcpenable=yes
tcpbindaddr=0.0.0.0
bindaddr=0.0.0.0
bindport=5060
context=general
srvlookup=yes

[ext2001]
type=friend
host=dynamic
context=phones

[ext2002]
type=friend
host=dynamic
context=phones

[ExchangeUM]
type=peer
host=192.168.37.22
transport=tcp
promiscredir=yes

extensions.conf

[global]

[general]

[default]

[phones]
include => internal

[internal]

exten => 7000,1,Dial(SIP/ExchangeUM/7000)
exten => 7000,n,Busy()

As you can see nothing complicated however I have attached the packet capture from Wireshark which essentially shows a normal SIP conversation right up until Asterisk sees the 302 at which point it all just stops.

Wireshark Packet Capture

Any help appreciated!
Cheers,
Tom

no one tried this :frowning: