you can try and locate the other subroutine / workflow using some sql queries
replace ZZZZ-Delete with subroutine name
USE CCMData
Select Name from tblConfig_VWM_Callflow
Where pkey in (
Select FKCallflow from tblConfig_VWM_CallflowSubroutineMembers
Where FKSubroutine in (Select pkey from...
seems to be yet another short sighted design from mitel - express also had a heap of limitations and then they gave up on it , wouldnt be surprised to see this go the same way
pretty sure its same as server gateway - public IP has to be applied directly to the interface
- effectively makes it useless for customer site installations as they hate that config
acd paths are used to break any integration - basically makes it forget the original diversion and work off of the interflow destination number instead
- sometimes without the acd path it doesn't matter what happens next it always tries to go to a mailbox related to the origination of the 1st...
i agree with nupoint not liking the * or #
try this ( using 9157 as available number - can be anything )
create nametag 9157 (ONLY if there are NO other nametags in call flow)
reroute Always 9157 to nupoint D N1 N2
add 9157 as additional number of mailbox 8157
set 10 extensions to reroute 1st...
get a packet capture - easy to read sip traffic and you can normally see what the issue is
sip tail on in maintenance commands - can paste the results in here
yeah , i feel your pain , unfortunately there seems to be a massive slow down in development - not sure if its budget based now that they have been purchased by a hedge fund or whether they are just spending all the money on expos like mitel next . dont hold you breath for any fancy features...
probably best to enter Question in english
"
Hello everyone,
I'm currently having an interconnect issue between Mitel EX and Avaya. The SIP cluster has been successfully established. The problem is, when the Mitel SIP phone calls the Avaya phone, both parties communicate fine, and the same goes...
not a fan - wont be back here as often as i used to be........
Interface is ok , new stuff is ok , hate the way teh forums are organises - cant work out hwo to make just the ones i want to look at be listed as they used to be.
And now im having to set any email notifications as spam because im...
FYI the DRNs and sys eng guide no longer include usefull information like compatible versions - they have references to the same crappo matrix
most of the recent versions go back to MIVB 8.0SP3 ( last version before vxworks change and additional RAM for physical servers )
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.