so APN is the way ... View more

yeah you should definitely add this advanced feature! it's a shame users cannot add SDblf on their own I guess Cisco would implement this feature if they had to pay 1$ for each SDblf converted to a SD ... View more

think i got it! should be explained here: Cisco DevNet: Administrative XML (AXL) - How To ... View more

can you point me to a collection of all the SOAP messages? I'm aware of the AXL Schema Reference but it's not like the SOAP message format you just posted. Again thanks a lot for your help! ... View more

Thanks a lot for your reply, much appreciated. What I'm trying to do is modify the axltoolkit class and create a partition to start then I'll do the same stuff for CSSs, Locations etc. But the below code is failing on the CUCM with this error: Request 1447928479783 was processed in 72ms 2015-12-02 12:39:55,006 INFO  [http-bio-443-exec-3] filters.TimingFilter - Received request 1447928479784 from administrator at IP 10.100.253.43 2015-12-02 12:39:55,006 DEBUG [http-bio-443-exec-3] wrappers.RequestHeaderWrapper - Inside Request Header Wrapper 2015-12-02 12:39:55,006 WARN  [http-bio-443-exec-3] wrappers.RequestHeaderWrapper - Client sent an unsupported header, SOAPAction= [CUCM:DB ver=10.5], attempting to auto correct. 2015-12-02 12:39:55,006 WARN  [http-bio-443-exec-3] wrappers.RequestHeaderWrapper - SOAPAction header correction needed: Api is malformed or missing 2015-12-02 12:39:55,011 DEBUG [http-bio-443-exec-3] filters.ThrottlingFilter - DBLCNQueue Count: 0 2015-12-02 12:39:55,012 DEBUG [http-bio-443-exec-3] filters.ThrottlingFilter - Successfully set the value of counter: 4 value: 0 2015-12-02 12:39:55,012 DEBUG [http-bio-443-exec-3] servletRouters.AXLAlpha - Checking request version [10.5] 2015-12-02 12:39:55,012 DEBUG [http-bio-443-exec-3] servletRouters.AXLAlpha - Checking if requested api [addRoutePartition] the implementedHandlers list 2015-12-02 12:39:55,012 DEBUG [http-bio-443-exec-3] servletRouters.AXLAlpha - [addRoutePartition] is not in the implementedHandlers list 2015-12-02 12:39:55,012 INFO  [http-bio-443-exec-3] servletRouters.AXLAlpha - Going to axis---> 2015-12-02 12:39:55,013 DEBUG [http-bio-443-exec-3] wrappers.RequestNamespaceWrapper - Inside Request Wrapper 2015-12-02 12:39:55,013 INFO  [http-bio-443-exec-3] servletRouters.AXLAlpha - AXL REQUEST : <SOAP-ENV:Envelope xmlns:SOAP-ENV=" http://schemas.xmlsoap.org/soap/envelope/ " xmlns:ns=" http://www.cisco.com/AXL/API/10.5 "><SOAP-ENV:Header/><SOAP-ENV:Body><ns:addRoutePartition><newPattern sequence="1449056395221"><name>PT-X-TEST1</name><description>PT site </description></newPattern></ns:addRoutePartition></SOAP-ENV:Body></SOAP-ENV:Envelope> 2015-12-02 12:39:55,013 DEBUG [http-bio-443-exec-3] servletRouters.AXLAlpha - Request processed by AXIS 2015-12-02 12:39:55,015 DEBUG [http-bio-443-exec-3] axlapiservice.Handler - dbConnector Initialization in handler.java 2015-12-02 12:39:55,015 DEBUG [http-bio-443-exec-3] axlapiservice.Axl - Connection given to current thread 2015-12-02 12:39:55,016 DEBUG [http-bio-443-exec-3] axlapiservice.Axl - Thread is same so connection is reused, name of thread : http-bio-443-exec-3 2015-12-02 12:39:55,017 DEBUG [http-bio-443-exec-3] axlapiservice.AXLCallFlow - In begin transaction of AXLCallflow and created pub connector 2015-12-02 12:39:55,017 DEBUG [http-bio-443-exec-3] axlapiservice.AddRoutePartitionHandler - In AddRoutePartition public SOAPMessage createSOAPMessage(String sPattern, String sPartition, String sCSS, String sMask) throws Exception {         MessageFactory mf = MessageFactory.newInstance();         SOAPMessage soapMessage = mf.createMessage();         MimeHeaders headers = soapMessage.getMimeHeaders();         headers.addHeader("SOAPAction", "CUCM:DB ver=10.5");         SOAPEnvelope envelope = soapMessage.getSOAPPart().getEnvelope();         SOAPBody bdy = envelope.getBody();         envelope.addNamespaceDeclaration("ns", " http://www.cisco.com/AXL/API/10.5 ");         SOAPBodyElement bodyElement = bdy.addBodyElement(envelope.createName("addRoutePartition"));         bodyElement.setPrefix("ns");                         Name attrUuid = envelope.createName("uuid");                 SOAPElement newPattern = bodyElement.addChildElement("newPattern");         newPattern.addAttribute(envelope.createName("sequence"), String.valueOf(System.currentTimeMillis()));         newPattern.addChildElement("name").addTextNode(sPattern);                newPattern.addChildElement("description").addTextNode(sCSS);                                      return soapMessage;     } ... View more

can you help me doing the same thing with java? I'm using the AXLtoolkit ... View more

very well done doc! I've a question regarding inter-cluster URI dialling. I have an ILS network setup between 2 leaf nodes and a SME. I'm using OTLD/FQDN example.com/cucm.example.com. The issue is that calls between phones registered to different leafs do not display as calling name: user@example.com instead just user. I've flagged the Use FQDN for SIP requests under the SIP profile assigned to each of the phones. Any suggestions? ... View more

try using h323 and check what dial-peers are matched. show call acti voi comp ... View more

Hello, I'm having your exact same issue but with hub in ver 10 and spoke in ver 9. If both have same ver. it works. How did you manage to fix the issue? ... View more

the dial-peer you posted is h323, I wouldn't make "transcoding" between h323 and SIP. The one you call building-router is most probably a router with a sip trunk to your provider. Here are multiple factors that may cause your issue: - transcoding between h323 and SIP - dtmf relay methods mismatch i.e on one router you have h245-alpha and on another rtp-nte - check what dial-peer are matched for a call when dtmf aren't working. You should have on both your routers SIP in/out dial-peers like the following. dial-peer voice 200 voip  description ## outgoing all ##  translation-profile outgoing outgoing-called  incoming called-n 9T  destination-pattern 9T  session target ipv4:172.16.34.100  ses pro sipv2   voice-class codec 1   ! voice-class h323 1  dtmf-relay  sip-kpml sip-notify  no vad ... View more

if you are talking about bad quality in phone calls have a look to the qos configured over the line between the two branches ... View more

you should also add the dn-webedit command ... View more

it's not clear what you have on the other side of this dial-peer. is it your isp? Maybe something changed on that side... dial-peer voice 200 voip  description ## outgoing all ##  translation-profile outgoing outgoing-called  destination-pattern 9T  session target ipv4:172.16.34.100  voice-class codec 1    voice-class h323 1  dtmf-relay  rtp-nte h245-alphanumeric  no vad ... View more