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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Aastra Mx-One transit call to A430 not working

Status
Not open for further replies.

ALEXROC

Programmer
Jan 17, 2014
11
SG
Hi All,

I have setup SIP trunk between Aastra MX-One to 2 xCisco CME and Aastra A430. MX-One also handle the routing for transit call (cisco to/from cisco and cisco to/from 430. Normal calls Aastra MX-One to/from all other working fine. Cisco to other Cisco calling through MX-One also ok. But when Cisco calls to Aastra A430, the call just re-route back to MX_one user@receptionist.( There is re-route feature enable which will re-route any calls that not able to establish due to digits not sending correctly or target destination can not reach). All SIP trunk setting for Cisco and A430 are exactly the same. MX-One can call to/from A430 with no issue. Only got issue with Cisco call to A430 through MX-One. A430 run the trace and didn't see any incoming traffic from MX-One.On MX-One trace, I saw the call coming from Cisco then with no reason it's just route to receptionist after few ring, didn't see the traffic sending to A430. But if Cisco call to/from other Cisco , I saw the incoming call received then MX-One re-direct the call to other Cisco. I dont understand why the call doesn't re-direct to A430 if we call from any Cisco. I have attached some configuration and traces.
Destination from MX-One : to A430 : 744 (not work) to CME :7864 (work) to CME: 7861 (work)
7864xxx call to/from 7861xxx ok. 7861/7864 call to/from 744xxxx not working.
Pls advise me if something need to be done on A430 or Cisco firewall/access list which may cause the issue. I am just handling MX-One and don't know much about A430 and Cisco CME.

MDSH>
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
100 7110000000000010 4 3100030001 0 30 128 00151515 3111101100A0 001100

101 7110000000000010 4 3100030001 0 30 128 00151515 3111101100A0 001100

102 7110000000000010 4 3100030001 0 30 128 00151515 3111101100A0 001100



END

MDSH> rocap:rou=100&&103;

ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
100 TL66 H'00000000 H'00000000 H'00000104 NO

101 TL66 H'00000000 H'00000000 H'00000104 NO

102 TL66 H'00000000 H'00000000 H'00000104 NO




route : 100
protocol = udp
uristring0 = sip:?@10.231.73.1
uristring1 =
uristring2 =
uristring3 =
uristring4 =
uristring5 =
uristring6 =
uristring7 =
fromuri0 =
fromuri1 =
fromuri2 =
fromuri3 =
fromuri4 =
fromuri5 =
fromuri6 =
fromuri7 =
remoteport = default
accept = ALL
priority = 255
match =
contextb0 =
contextb1 =
contextb2 =
contextb3 =
contextb4 =
contextb5 =
contextb6 =
contextb7 =
contexta0 =
contexta1 =
contexta2 =
contexta3 =
contexta4 =
contexta5 =
contexta6 =
contexta7 =
authname =
password =
realm =
register = NO_REG
trusted = NO_TRUSTED
sosanumber =
sosaton =
sosdestnumber =
challenge = no
supervise = NO_SUPERVISION
supervisetime = 0
rexstring =
rexfromuri =


MDSH> sip_route -print -route 1001
Route data for SIP destination

route : 101
protocol = udp
uristring0 = sip:?@10.220.39.141
uristring1 =
uristring2 =
uristring3 =
uristring4 =
uristring5 =
uristring6 =
uristring7 =
fromuri0 =
fromuri1 =
fromuri2 =
fromuri3 =
fromuri4 =
fromuri5 =
fromuri6 =
fromuri7 =
remoteport = 5060
accept = ALL
priority = 255
match =
contextb0 =
contextb1 =
contextb2 =
contextb3 =
contextb4 =
contextb5 =
contextb6 =
contextb7 =
contexta0 =
contexta1 =
contexta2 =
contexta3 =
contexta4 =
contexta5 =
contexta6 =
contexta7 =
authname =
password =
realm =
register = NO_REG
trusted = NO_TRUSTED
sosanumber =
sosaton =
sosdestnumber =
challenge = no
supervise = NO_SUPERVISION
supervisetime = 0
rexstring =
rexfromuri =


MDSH> sip_route -print -route 1012
Route data for SIP destination

route : 102
protocol = udp
uristring0 = sip:?@10.231.67.250
uristring1 =
uristring2 =
uristring3 =
uristring4 =
uristring5 =
uristring6 =
uristring7 =
fromuri0 =
fromuri1 =
fromuri2 =
fromuri3 =
fromuri4 =
fromuri5 =
fromuri6 =
fromuri7 =
remoteport = default
accept = ALL
priority = 255
match =
contextb0 =
contextb1 =
contextb2 =
contextb3 =
contextb4 =
contextb5 =
contextb6 =
contextb7 =
contexta0 =
contexta1 =
contexta2 =
contexta3 =
contexta4 =
contexta5 =
contexta6 =
contexta7 =
authname =
password =
realm =
register = NO_REG
trusted = NO_TRUSTED
sosanumber =
sosaton =
sosdestnumber =
challenge = no
supervise = NO_SUPERVISION
supervisetime = 0
rexstring =
rexfromuri =

MDSH> roddp:dest=701;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
791 102 1005000000000250000000000000 0 4 0

MDSH> roddp:dest=701;44;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
744 100 1005000000000250000000000000 0 4 0

MDSH> roddp:dest=7861;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
7864 101 1005000000000250000000000000 0 4 0
 
 http://files.engineering.com/getfile.aspx?folder=1d6e7ea7-d360-4d67-9fa6-ce80110ab406&file=SIPLP_Cisco-to-Cisco_working
Hi Previous attached is working SIPLP trace which you can see MX-One received the call from Cisco and then re-form the SIP info and re-direct to another Cisco and call successfully established.

Below attached is the call which failed. I saw MX-One received the call but didn't see the re-direct.

Please assist if someone found what caused the issue or any advice.


Thanks!
 
 http://files.engineering.com/getfile.aspx?folder=ef88829a-8a82-45e3-9c9c-b5254579f829&file=SIPLP1_Cisco_to_A430_not_work
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top