sundance-communications.com/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems Posted for Gobaldata

Have a Mitel 3300 and am trying to connect it to an Adit 3504 SIP gateway with PRI ports Both sides seem to be functioning properly but get no cross talk between the 2 systems. Any insight would be appreciated.

Nailed up connection but no talk path on IP is often because router/gateway UDP ports are not configured.

This might be a configuration issue on the Adit 3504. It seems the Inbound SIP are not being routed to the PRI trunks. Is anyone familiar with configuring the Adit 3504?

I added the number to the T1 Pri trunk and when the sip call comes in I get a circuits busy. If I take it out of the t1 PRI I get out of service. So it is recognizing the number as it comes it but does not seem to send it out the PRI trunk to the Mitel? Any insights?

Anyone familiar with configuring a Adit 3504 as a SIP to PRI Gateway? Please let me know and I would greatly appreciate your assistance. I follwed the manual to a tee but the documentation is very limited and has no troubleshooting section at all.

Additional info... the Adit 3504 Gateway is sitting on a public IP with a direct connection to the Mitel 3300 NSU L0/L1 connections. There is no port forwarding or NAT involved.

This is what the SIP log gives me on an inbound call:
Receive: Tue Jan 11 22:35:32.402 2011
Trunk 1:15598024267 Src: 209.216.2.211:5060
INVITE sip:15598024267@65.115.68.123:5060;user=phone;transport=UDP SIP/2.0
Record-Route: <sip:209.216.2.211;lr=on;ftag=3c4-45026-81d96a-2e52a02-81d96a>
Via: SIP/2.0/UDP 209.216.2.211;branch=z9hG4bK5198.faa54804.0
v: SIP/2.0/UDP 65.243.172.245:5060;branch=z9hG4bK87b855c9bd8f9bf2c10583394792c590.2d8b6288
Record-Route: <sip:65.243.172.245:5060;lr>
v: SIP/2.0/UDP 65.243.172.235:5060;branch=z9hG4bK9493dc2fd1f0e7cacf373dd5653faec9.508b6672;received=65.243.172.235
Record-Route: <sip:65.243.172.235;lr>
Remote-Party-ID: <sip:+18055044701@65.243.172.235>;screen=yes;party=calling;privacy=off
f: <sip:+18055044701@199.173.94.152:5060;user=phone>;tag=3c4-45026-81d96a-2e52a02-81d96a
t: <sip:+15598024267@65.243.172.235:5060;user=phone>
i: 41048cd0985eadc713c481d96afb3948a9fb5f423e26c3e860-0086-6431
CSeq: 1 INVITE
Allow: ACK,BYE,CANCEL,INVITE,OPTIONS,INFO,SUBSCRIBE,REFER,NOTIFY,PRACK
v: SIP/2.0/UDP SCR9:5060;maddr=199.173.94.152;branch=z9hG4bK-81d96a-fb3948a9-4fb1e563;received=199.173.94.152
Max-Forwards: 17
m: <sip:199.173.94.152:5060;transport=UDP>
k: 100rel, replaces
c: application/sdp
l: 233

v=0
o=PVG 1294784290190 1294784290190 IN IP4 199.173.77.46
s=-
p=+1 6135555555
c=IN IP4 199.173.77.46
t=0 0
m=audio 53328 RTP/AVP 18 0 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=fmtp:18 annexb=no


2: Send: Tue Jan 11 22:35:32.415 2011
Trunk 1:+15598024267 Dest: 209.216.2.211:5060
SIP/2.0 100 Trying
f: <sip:+18055044701@199.173.94.152:5060;user=phone>;tag=3c4-45026-81d96a-2e52a02-81d96a
t: <sip:+15598024267@65.243.172.235:5060;user=phone>;tag=4173447b-13c4-4d2cdb34-1518d-30112a05
Call-ID: 41048cd0985eadc713c481d96afb3948a9fb5f423e26c3e860-0086-6431
CSeq: 1 INVITE
Via: SIP/2.0/UDP 209.216.2.211;branch=z9hG4bK5198.faa54804.0
v: SIP/2.0/UDP 65.243.172.245:5060;branch=z9hG4bK87b855c9bd8f9bf2c10583394792c590.2d8b6288
v: SIP/2.0/UDP 65.243.172.235:5060;received=65.243.172.235;branch=z9hG4bK9493dc2fd1f0e7cacf373dd5653faec9.508b6672
v: SIP/2.0/UDP SCR9:5060;maddr=199.173.94.152;received=199.173.94.152;branch=z9hG4bK-81d96a-fb3948a9-4fb1e563
Supported: replaces
Server: CarrierAccess-Adit3500/1.6.0.34
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, INFO
Contact: <sip:15598024267@65.115.68.123:5060;transport=UDP;user=phone>
Content-Length: 0



3: Send: Tue Jan 11 22:35:32.423 2011
Trunk 1:+15598024267 Dest: 209.216.2.211:5060
SIP/2.0 503 Service Unavailable
f: <sip:+18055044701@199.173.94.152:5060;user=phone>;tag=3c4-45026-81d96a-2e52a02-81d96a
t: <sip:+15598024267@65.243.172.235:5060;user=phone>;tag=4173447b-13c4-4d2cdb34-1518d-30112a05
Call-ID: 41048cd0985eadc713c481d96afb3948a9fb5f423e26c3e860-0086-6431
CSeq: 1 INVITE
Via: SIP/2.0/UDP 209.216.2.211;branch=z9hG4bK5198.faa54804.0
v: SIP/2.0/UDP 65.243.172.245:5060;branch=z9hG4bK87b855c9bd8f9bf2c10583394792c590.2d8b6288
v: SIP/2.0/UDP 65.243.172.235:5060;received=65.243.172.235;branch=z9hG4bK9493dc2fd1f0e7cacf373dd5653faec9.508b6672
v: SIP/2.0/UDP SCR9:5060;maddr=199.173.94.152;received=199.173.94.152;branch=z9hG4bK-81d96a-fb3948a9-4fb1e563
Supported: replaces
Server: CarrierAccess-Adit3500/1.6.0.34
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, INFO
Content-Length: 0