Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Inter-PBX SIP Route 1

Status
Not open for further replies.

UKTurnip

Technical User
Aug 21, 2009
22
0
0
GB
Hi

Has anyone on here set up a SIP route between an MX-One and another PBX (particularly Mitel MN3300)?

Any config prints from a working inter-PBX SIP route would be appreciated as I am struggling to understand the examples given in the Astra documentation which only appear to show a PBX to exchange configuration.

Ultimately I need to get this working between both a Ver 3.2 and a Ver 4.0 MX-One back to a Mitel switch.

Any help and/or comments would be appreciated.
 
Hi, this sip route work fine with Asterisc.
can you try.
Route data for SIP destination

Route : 100
Protocol = udp
Invite URI string 0 = sip:?@10.7.41.3 (ip Asterisc)
Invite URI string 1 =
Invite URI string 2 =
Invite URI string 3 =
Invite URI string 4 =
Invite URI string 5 =
Invite URI string 6 =
Invite URI string 7 =
From URI string 0 = sip:?@10.7.25.11 (ip asu-e mxone)
From URI string 1 =
From URI string 2 =
From URI string 3 =
From URI string 4 =
From URI string 5 =
From URI string 6 =
From URI string 7 =
Port = default
Accepted calls = ALL
Priority = 255
Match this =
context B-party 0 =
context B-party 1 =
context B-party 2 =
context B-party 3 =
context B-party 4 =
context B-party 5 =
context B-party 6 =
context B-party 7 =
context A-party 0 =
context A-party 1 =
context A-party 2 =
context A-party 3 =
context A-party 4 =
context A-party 5 =
context A-party 6 =
context A-party 7 =
Authentication username =
Password =
Realm =
Registration type = NO_REG
Trusted privacy domain = no
SOS a subscriber number =
SOS type of number =
SOS destination number =


LIM1:/home/eri_sn_admin # rodap:rou=100;
bash: rodap:rou=100: command not found
LIM1:/home/eri_sn_admin # mdsh
MDSH> rodap:rou=100;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
100 TL66 H'00000000 H'00000000 H'00000111 NO



END

MDSH> rocap:rou=100;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
100 7110000000000010 4 31100000001 0 30 128 00151515 0111111000A0 001100



END

MDSH> roddp:dest=5901;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
5901 100 000500000000025000000000000 0 1 0




\Satellite1900
 
Thanks for the prompt response. It was useful to validate our settings were were ironically correct.

Our problem (now sorted) was that we entered our actual server addresses, whereas we should have entered our alias addresses which we have assigned to the MX-One.
 
it's correct.
if you have an alias address, you must use it.

\Satellite1900
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top