Slow JDBC calls with wrong configured DNS

We recently found out that a wrong configured DNS Server can cause oracle JDBC Clients to react extremly slow. (1 second per simple sql statment)
We have found also that if the DNS server is disabled on server side (8.1.7.1 Oracle, Redhat 6.2 server) the system responds with normal speed.
It seems for us that Reverse lookups are done for any SQL Statement sent from the client and not only for the first connection.
Does anybody know how to disable this Reverse DNS-Lookups on Server side because this may also cause a slowdown if the DNS-Server is correctly configured or all clients are defined in /etc/hosts.
Thank you in advance!

Similar Messages

Performance - using JDBC call with 'order by' vs sorting data on app server

Hello! I need some valid thoughts on the performance of using a JDBC call versus processing information on the application server.
Here is the somewhat simplified scenario:
I need to retrieve customer information (name, e-mail, telephone), display it in HTML format and then be able to redisplay it in a different order. For example, initially the list would be displayed sorted by last name, but then a user might choose to sort it by e-mail address. Initial call to DB uses 'order by' in the SQL stmt to get me the initial ordering by last name. Results are stored in 2D array. However, when a user selects a different sort I have two options:
1) just make another call to the DB with a different order by clause. This means I need to create a DB connection, connect to DB, retrieve the results and read them from result set into a 2 dimensional array
2) re-sort data in the 2D array populated during the initial call. This means I need to use java.util.Arrays.sort(my_2D_resultsArray, my_custom_comparator)
Question is : which is more efficient? Number of entries retrieved can be anywhere from 0 to a few thousands (depending on other filters such as customer's country). My feeling is that option umber 2 is better, but I would like to get your opinion.
Thank you!

Good points! Thanks! I ran a test (see code below) and it takes less than a second to sort 2000 Strings and 2000 nulls. The only thing I ran the test at a UNIX prompt as oppose to from within app server (Weblogic). I expect the speed to be compatible though. Do you think that test was valid and tells us that sorting on the app server is probably faster than doing another SQL query?
import java.io.*;
import java.math.*;
import java.util.*;
import java.util.Arrays.*;
public class Test {
public static void main(String[] args) throws Exception {
    Test test = new Test();
    test.testSortingPerformance();
public void testSortingPerformance() {
    Object[] objArray2 = new Object[]{};
    Vector v = new Vector();
    Date start, end;
    java.util.Random rd = new java.util.Random(2000);
    for (int i = 0; i < 2000; i++){
      v.add(new Object[]{new String("" + rd.nextInt())});
      v.add(new Object[]{null});
    objArray2 = v.toArray();
    Object[] innerObjArray2 = new Object[]{};
    MyComparator2 myComp = new MyComparator2();
    start = new Date();
    java.util.Arrays.sort(objArray2, myComp);
    end = new Date();
    for (int i = 0; i < objArray2.length; i++) {
      System.out.println();
      innerObjArray2 = (Object[])objArray2;
for (int j = 0; j < innerObjArray2.length; j++) {
System.out.print(innerObjArray2[j] + " ");
System.out.println(v.size());
System.out.println("Start " + start + " End " + end);
import java.util.*;
public class MyComparator2
implements Comparator {
//position in the inner array to use for comparison
private int position = 0;
//default empty constructor
public MyComparator2() {
//implement compare method
public int compare(Object o1, Object o2) {
Object[] strAr1 = (Object[]) o1;
Object[] strAr2 = (Object[]) o2;
if (strAr1[0] == null){
if (strAr2[0] == null){
return 0;
else{
return -1;
else if (strAr2[0] == null){
return 1;
return ( (String) strAr1[0]).compareTo( (String) strAr2[0]);

With JDBC, calling a stored procedure with ARRAY as out parameter

Hi,
I want to use the data type ARRAY as an out parameter in an Oracle stored procedure. I want to call the stored procedure from
my java program using JDBC.
The problem it's i use a 8.1.7 client to acces with oci to a 7.1.3 Database.
With this configuration I can get back a Cursor but not an Array.
Does it's possible ?
Thanks for your help !
Michakl

Originally posted by JDBC Development Team:
It's very similar to other datatype except that it uses OracleTypes.ARRAY typecode and the value is mapped to a oracle.sql.ARRAY instance. The code looks as follows --
cstmt.registerOutParameter (idx, OracleTypes.ARRAY, "VARRAY_TYPE_NAME_HERE");
cstmt.execute ();
ARRAY array = (ARRAY) cstmt.getObject (idx);
Thanks for your reply.
I have to use:-
OracleCallableStatement cs1 = (OracleCallableStatement )conn.prepareCall
( "{call proj_array(?)}" ) ;
for retrieving a collection as an OUT parameter.
This gives me the errors:-
C:\jdbc\VarraySQL.java:0: The method oracle.jdbc2.Blob getBlob(int) declared in class oracle.jdbc.driver.OracleCallableStatement cannot override the method of the same signature declared in interface java.sql.CallableStatement. They must have the same return type.
import java.sql.*;
^
C:\jdbc\VarraySQL.java:0: The method oracle.jdbc2.Array getArray(int) declared in class oracle.jdbc.driver.OracleCallableStatement cannot override the method of the same signature declared in interface java.sql.CallableStatement. They must have the same return type.
import java.sql.*;
^
C:\jdbc\VarraySQL.java:0: The method oracle.jdbc2.Clob getClob(int) declared in class oracle.jdbc.driver.OracleCallableStatement cannot override the method of the same signature declared in interface java.sql.CallableStatement. They must have the same return type.
import java.sql.*;
^
C:\jdbc\VarraySQL.java:0: The method oracle.jdbc2.Ref getRef(int) declared in class oracle.jdbc.driver.OracleCallableStatement cannot override the method of the same signature declared in interface java.sql.CallableStatement. They must have the same return type.
import java.sql.*;
^
How do I get rid of these errors?
null

First webservice call with UTL_HTTP is slow

Hi,
When i do several webservice calls with the utl_http methods, the first webservice call takes a lot of time (sometimes more than 10-20 seconds). Every other webservice call (after this one) goes very fast (not even a second).
Any ideas to make that first call faster?
Thx.

Davy wrote:
When i do several webservice calls with the utl_http methods, the first webservice call takes a lot of time (sometimes more than 10-20 seconds). Every other webservice call (after this one) goes very fast (not even a second).Don't see how this is an Oracle problem.
Oracle creates a tcp socket and makes a socket call using the http application protocol. If this is slow, then there is either a performance issue at networking level, or a performance issue at the remote server that accepts and services the tcp connection.
Network level - as Sybrand mentioned, it can be DNS related. You make the call using a hostname. That hostname needs to be resolved into an IP address. The network layer is slow (because of a problematic DNS server for example) to resolve that hostname into an IP address. Similar thing can be happening on the web server side. Reverse DNS lookup is used to determine what the hostname of the Oracle server is, using the IP address of the incoming connection.
The web server/service can be slow - the 1st request may make a lot of physical I/O calls. The kernel buffers the data. Subsequent I/O from this web service servicing new calls finds the data in the file cache via must faster logical I/O.
So you need to isolate and monitor these layers, the network and the web server, to determine what the reason is for the 1st call to be seemingly slow and subsequent calls not.

What's wrong with my device? It does not allow me to make calls with Skype or Viber... Can someone help?

What's wrong with my device? It does not allow me to make calls with Skype or Viber... Can someone help?

My device is a Blackberry Z30. Skype and Viber just to work fine. I had to travel abroad and turn off data services while traveling outside of the US but the applications worked just fine with Wi-Fi. Suddenly they stopped working to make calls. I can still send text messages, but when I try to do a voice or video call (in the case of skype), it only says "failed call" and when I try to call using Viber I get an error message that says the I can not use the application until I complete my GMS call which is ridiculous because I'm not using the phone other than trying to place my call through Viber. The interesting thing is that when I go the permission page in my security settings everything indicates that its on but is gray out and I do not have access to change any setting. The same in both applications. The rest of the applications are accessible to change settings. I already uninstalled skype and reinstalled it and still the same problem. I'm ready to back up everything and wipe out the device to original settings.

Configure DNS on Snow Leopard for private NAT with Open Directory

I am needing to set up DNS on Snow Leopard server 10.6.4 for use with Snow Leopard clients only. On the server, I have two IPs, one public connections outside the network, and one private within the NAT range. DNS was not originally set up on the server, but Open Directory was (sort of). I've demoted the server from OD master to stand alone, but still can't get this to work.
This server is only for setting up and using Open Directory + NetInstall services inside the network. In effect, it isn't serving web pages and isn't registered with our upstream DNS. What I am assigned to do is get Open Directory to set up user profiles and network shares and home directories. So, what I need is this -
a basic DNS config I can do in Server Admin that will set up DNS to resolve to the local server NAT IP for Open Directory purposes;
and provide DNS for outside the OS X server for the specified Snow Leopard clients.
DHCP is running (but the clients were configured with static IPs in the NAT range). This serves as the DHCP server for the entire network (Windows + Mac clients that aren't in the static NAT range).

Thanks for your replies. I realize I'm not making clear the way this network is configured . Also, the only services running on the Snow Leopard server are (at this time):
dhcpd - in the 10.136.31.x range;
dns - same as before;
planned to add are:
Open Directory (for network logins)
Software update;
Web (only on the 10.136.31.x Ethernet);
mySQL (localhost only - for moodle);
NAT is not set up on the Snow Leopard server itself. We have an outside router, a Cisco 2811. This router provides routing for both the public IP range, and the NAT range is configured in this router. The forwarding dns is located in LR and Fayetteville. So what I need is dns on Snow Leopard to forward outside queries to the state DNS servers, and resolve the local NAT IP only for Open Directory and a set of Snow Leopard clients.
Is this going to be possible?

Configuring JDBC connector with my Tomcat server

I realize this may be a dumb question, but I'm having trouble configuring my JDBC connector with my tomcat server. I'm trying to run a simple servlet that will access mysql database. I am almost certain its throwing an exception on the line:
Class.forName("com.mysql.JDBC.Driver");
I have a feeling the tomcat class path isn't finding the connector jar file.
Any help would be greatly appreciated.
Brian

I am almost certain its throwing an exception on the line:
Class.forName("com.mysql.JDBC.Driver");If it's a ClassNotFound exception or the like, then yes. Post the exception and stack trace if you need confirmation of this.
I have a feeling the tomcat class path
isn't finding the connector jar file.That's what I think too. Did you ensure that the MySQL driver JAR file was in the classpath?
It will need to be in common/lib under Tomcat, or WEB-INF/lib under your application.
For a more portable application you should use JNDI to obtain database connection resources, in which case you would want the JAR to be under common/lib.

HELP - hi with apple Configurator why does it show with a yellow triangle on the right side of the screen what am i doing wrong for the ipads not syncing or whatever and how do i fix that?

HELP -- hi with apple Configurator why does it show with a yellow triangle on the right side of the screen what am i doing wrong for the ipads not syncing or whatever and how do i fix that? although i have looked online to try and figure it out and here is the website i found is this the stuff i need to do to fix this? is this site what i need to do to fix this? http://edtechstandish.wordpress.com/what-ive-learned-about-apple-configurator-so -far/ Thanks

Sorry but I don't know anything about this. But you might have better luck posting this question over ing the iPad in Business and Education forum here: https://discussions.apple.com/community/ipad/ipad_in_business_and_education?view =discussions.

Tell me what is ******* going on!!!????! The time and date issues!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Every times I went to Apple store, the phone automatically works good time, but when I came back, my phone is working very slow with wrong time!

The time and date issues!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Every times I went to Apple store, the phone automatically works good time, but when I came back, my phone is working very slow with wrong time!
I want to get a new iPhone to replace this defective phone. I am gonna be crazzzzzzzyyyyyyyy with anger,!!!,!,,,! I takes2 hours to go to Regent street apple stores for three times!!!!!. It is a lot of transport fees !
PLz tell me why! How to deal with it !

Unless it's confirmed officially that your phone is defective, then you can ask for a replacement. Or you have to live with you. However you can trade it for a new one if you don't care the price drop.

There is a problem with the phone app. When I want to call somebody the phone screen come too late. This will cause a problem if I call the wrong number

There is a problem with the phone app. When I want to call somebody the phone screen come too late. This will cause a problem if I call the wrong number. Apple please please please fix it as soon as possible and also check why the phone is always restart. I prefer to let us use the iOS 7 until you finished from the IOS 8 because Ios 8 still under construction there is a tones problems in the system. And this Will cause undirect problem for the iPhone 6

There is no apple here in this user to user technical forum.
Do this Use iTunes to restore your iOS device to factory settings

AEX CS3 error {SetOutputWorld called with a world of the wrong size}

I am getting the following message:
After Effects error: internal verification failure, sorry! {SetOutputWorld called with a world of the wrong size}
( 78 :: 4 )
Any suggestions?

Check this:
http://aeerrors.myleniumstuff.de/?p=547
Beyond that, you will have to provide more info on what you actually do. Could be a couple of things from the CoDec issues mention in my collection to outdated plug-ins doing something weird...
Mylenium

Configuring DNS servers with PPPoE

Hi all,
just received my base station, I'm trying to configure a custom couple of dns servers ( usually I work with opendns instead of the default ones from my ISP ) but after checking I notice that base station is still working with the default dns of my ISP. I tried to reset and re-configure the PPPoE connection but it still doesn't work.
Any suggestion?

Hello again, I feel sort of annoying by posting so many things.
I created a user in DC3 and it was replicated to DC1-New. If I do it the other way around, it does not work.
In other words, the replication process only works this way DC3 --> DC1-New. I have checked it is not a firewall issue, all are off, since I began this lab.
If I run repadmin /showrepl in DC1-New ,
it sees DC3 and all success messages regarding the replication.
If I run repadmin /showrepl in DC3,
it just sees nothing.
I also run dcdiag /test:knowsofroleholders in DC3 and
there is this message: The holder of the Schema master is a deleted DC (DC1) . The same of all the 5 FSMOs.
I am trying to find a way to tell DC3 that the FSMOs holder is not DC1, but DC1-New.
Thanks for your support.
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

Issue with logging to the device after wrongly configured TACACS

Hell All,
We are unable to login to the device after we wrongly configured AAA on Cisco 881 Router and unfortunately we have saved the configuration.
Can you please help to either remove the remove the TACACS configuration or how we can reset the password without erasing the configuration?
Thanks a lot in advance for your help.
Regards,
Thiyagu

Look for password recovery. Not difficult if you have console access.
Sent from Cisco Technical Support iPad App

Please help with SIP configuration on 2801 router

Hi All.
Please help me to setup a SIP account. I’m already struggling to do that for a few days, and can’t find out how to finish that. We have 2xISDN lines running, so I need to add a SIP trunk to existing config.
The information from our SIP provider:
We have issued the following DDI range: 018877000 – 99
There is no need to register the DDI’s as these will be offered to your PABX IP address provided to in the completed SIP trunking form.
Configuration details are as follows:
Our Primary Proxy:-        99.234.56.78
Codec supported:-             G711Alaw, G729 (G711Alaw is the preferred codec)
Fax Support:-                     T38 and G711Alaw
DTMF:-                                 RFC2833 and INFO
CLI Method:-                     Remote-Party-ID
Trunk doesn’t require registration; you just need to send Invite. In cisco this is done through Dial-peer session-target command. We are authenticating your IP address for outgoing calls and incoming calls we then forward to the IP mentioned in the sip form.
This is a SIP configuration on Cisco2801 router (I used outgoing calls only):
translation-rule 10
Rule 0 ^90 0
Rule 1 ^91 1
Rule 2 ^92 2
Rule 3 ^93 3
Rule 4 ^94 4
Rule 5 ^95 5
Rule 6 ^96 6
Rule 7 ^97 7
Rule 8 ^98 8
Rule 9 ^99 9
interface FastEthernet0/0.1
description ***DATA VLAN***
encapsulation dot1Q 1 native
ip address 10.1.1.101 255.255.255.0
interface FastEthernet0/0.2
description ***VOICE VLAN***
encapsulation dot1Q 2
ip address 192.168.22.1 255.255.255.0
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
h323
call start slow
sip
bind control source-interface FastEthernet0/0.2
bind media source-interface FastEthernet0/0.2
registrar server expires max 36000 min 600
voice class codec 1
codec preference 1 g729r8
codec preference 2 g711ulaw
codec preference 3 g711alaw
dial-peer voice 1 pots
description ### External Dialling via BRI ###
preference 7
destination-pattern 9T
translate-outgoing called 10
direct-inward-dial
port 0/0/0
forward-digits all
dial-peer voice 2 pots
description ### External Dialling via BRI ###
preference 2
destination-pattern 9T
translate-outgoing called 10
direct-inward-dial
port 0/0/1
forward-digits all
dial-peer voice 9000 voip
description ** Outgoing calls to SIP **
preference 1
destination-pattern 9T
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target ipv4:99.234.56.78:5060
dtmf-relay rtp-nte
codec g711alaw
no vad
sip-ua
timers connect 100
sip-server ipv4:99.234.56.78
I used debugging commands to troubleshoot the calls.
2801(config-dial-peer)#
094509: Jan 24 09:27:06.204: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=211, Called Number=, Voice-Interface=0x65FA35B4,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
094510: Jan 24 09:27:06.204: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20018
094511: Jan 24 09:27:06.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9, Peer Info Type=DIALPEER_INFO_SPEECH
094512: Jan 24 09:27:06.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9
094513: Jan 24 09:27:06.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094514: Jan 24 09:27:06.716: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094515: Jan 24 09:27:06.816: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=90, Peer Info Type=DIALPEER_INFO_SPEECH
094516: Jan 24 09:27:06.816: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90
094517: Jan 24 09:27:06.816: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094518: Jan 24 09:27:06.816: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094519: Jan 24 09:27:06.912: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=908, Peer Info Type=DIALPEER_INFO_SPEECH
094520: Jan 24 09:27:06.912: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=908
094521: Jan 24 09:27:06.916: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094522: Jan 24 09:27:06.916: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094523: Jan 24 09:27:07.012: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9086, Peer Info Type=DIALPEER_INFO_SPEECH
094524: Jan 24 09:27:07.012: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9086
094525: Jan 24 09:27:07.016: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094526: Jan 24 09:27:07.016: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094527: Jan 24 09:27:07.116: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=90862, Peer Info Type=DIALPEER_INFO_SPEECH
094528: Jan 24 09:27:07.116: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862
094529: Jan 24 09:27:07.116: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094530: Jan 24 09:27:07.116: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094531: Jan 24 09:27:07.212: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=908621, Peer Info Type=DIALPEER_INFO_SPEECH
094532: Jan 24 09:27:07.212: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=908621
094533: Jan 24 09:27:07.216: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094534: Jan 24 09:27:07.216: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094535: Jan 24 09:27:07.316: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9086215, Peer Info Type=DIALPEER_INFO_SPEECH
094536: Jan 24 09:27:07.316: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9086215
094537: Jan 24 09:27:07.316: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094538: Jan 24 09:27:07.316: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094539: Jan 24 09:27:07.412: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=90862157, Peer Info Type=DIALPEER_INFO_SPEECH
094540: Jan 24 09:27:07.412: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862157
094541: Jan 24 09:27:07.416: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094542: Jan 24 09:27:07.416: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094543: Jan 24 09:27:07.516: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=908621577, Peer Info Type=DIALPEER_INFO_SPEECH
094544: Jan 24 09:27:07.516: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=908621577
094545: Jan 24 09:27:07.516: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094546: Jan 24 09:27:07.516: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094547: Jan 24 09:27:07.612: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9086215777, Peer Info Type=DIALPEER_INFO_SPEECH
094548: Jan 24 09:27:07.612: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9086215777
094549: Jan 24 09:27:07.616: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094550: Jan 24 09:27:07.616: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094551: Jan 24 09:27:07.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
094552: Jan 24 09:27:07.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862157774
094553: Jan 24 09:27:07.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
094554: Jan 24 09:27:07.716: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
094555: Jan 24 09:27:10.711: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=90862157774T, Peer Info Type=DIALPEER_INFO_SPEECH
094556: Jan 24 09:27:10.711: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862157774T
094557: Jan 24 09:27:10.711: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
094558: Jan 24 09:27:10.711: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=9000
     2: Dial-peer Tag=2
     3: Dial-peer Tag=1
094559: Jan 24 09:27:10.711: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=90862157774, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
094560: Jan 24 09:27:10.711: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862157774
094561: Jan 24 09:27:10.715: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
094562: Jan 24 09:27:10.715: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=9000
     2: Dial-peer Tag=2
     3: Dial-peer Tag=1
094563: Jan 24 09:27:10.715: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=90862157774, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
094564: Jan 24 09:27:10.715: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=9000
094565: Jan 24 09:27:10.715: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
094566: Jan 24 09:27:10.715: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862157774
094567: Jan 24 09:27:10.715: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
094568: Jan 24 09:27:10.715: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=9000
     2: Dial-peer Tag=2
     3: Dial-peer Tag=1
094569: Jan 24 09:27:10.719: fb_get_reject_cause_code: ERROR cause_code NULL
094570: Jan 24 09:27:10.727: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.1:5060;branch=z9hG4bK47D116D3
Remote-Party-ID: "Sam " <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Sam " <sip:[email protected]>;tag=CDCFB8AC-F98
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 09:27:10 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1787264879-1168380385-2421457215-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327397230
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 3237 2021 IN IP4 192.168.22.1
s=SIP Call
c=IN IP4 192.168.22.1
t=0 0
m=audio 18258 RTP/AVP 8 101
c=IN IP4 192.168.22.1
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
094571: Jan 24 09:27:11.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.1:5060;branch=z9hG4bK47D116D3
Remote-Party-ID: "Sam" <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Sam " <sip:[email protected]>;tag=CDCFB8AC-F98
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 09:27:11 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1787264879-1168380385-2421457215-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327397231
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 3237 2021 IN IP4 192.168.22.1
s=SIP Call
c=IN IP4 192.168.22.1
t=0 0
m=audio 18258 RTP/AVP 8 101
c=IN IP4 192.168.22.1
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
094572: Jan 24 09:27:12.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.1:5060;branch=z9hG4bK47D116D3
Remote-Party-ID: "Sam " <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Sam " <sip:[email protected]>;tag=CDCFB8AC-F98
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 09:27:12 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1787264879-1168380385-2421457215-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327397232
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 3237 2021 IN IP4 192.168.22.1
s=SIP Call
c=IN IP4 192.168.22.1
t=0 0
m=audio 18258 RTP/AVP 8 101
c=IN IP4 192.168.22.1
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
094573: Jan 24 09:27:14.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.1:5060;branch=z9hG4bK47D116D3
Remote-Party-ID: "Sam" <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Sam" <sip:[email protected]>;tag=CDCFB8AC-F98
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 09:27:14 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1787264879-1168380385-2421457215-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327397234
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 3237 2021 IN IP4 192.168.22.1
s=SIP Call
c=IN IP4 192.168.22.1
t=0 0
m=audio 18258 RTP/AVP 8 101
c=IN IP4 192.168.22.1
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
I made some changes in the router configuration.
I removed FA0/0.2 Voice interface from Voice service voip configuration (bind control source-interface FastEthernet0/0.2 and bind media source-interface FastEthernet0/0.2). And now it’s using ip address 10.1.1.101 (data ip).
The debugging is changed now. I can send and receive a respond from SIP server. But It shows an error: SIP/2.0 404 Not Found
Then it moves to ISDN line, and use this line to make a call.
102988: Jan 24 14:45:47.290: //-1/EDCA21089304/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=90862157774T, Peer Info Type=DIALPEER_INFO_SPEECH
102989: Jan 24 14:45:47.290: //-1/EDCA21089304/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862157774T
102990: Jan 24 14:45:47.290: //-1/EDCA21089304/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
102991: Jan 24 14:45:47.290: //-1/EDCA21089304/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=9000
     2: Dial-peer Tag=2
     3: Dial-peer Tag=1
102992: Jan 24 14:45:47.290: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=90862157774, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
102993: Jan 24 14:45:47.290: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862157774
102994: Jan 24 14:45:47.294: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
102995: Jan 24 14:45:47.294: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=9000
     2: Dial-peer Tag=2
     3: Dial-peer Tag=1
102996: Jan 24 14:45:47.294: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=90862157774, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
102997: Jan 24 14:45:47.294: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=9000
102998: Jan 24 14:45:47.294: //-1/EDCA21089304/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
102999: Jan 24 14:45:47.294: //-1/EDCA21089304/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862157774
103000: Jan 24 14:45:47.294: //-1/EDCA21089304/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
103001: Jan 24 14:45:47.294: //-1/EDCA21089304/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=9000
     2: Dial-peer Tag=2
     3: Dial-peer Tag=1
103002: Jan 24 14:45:47.298: fb_get_reject_cause_code: ERROR cause_code NULL
103003: Jan 24 14:45:47.310: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK4875CB9
Remote-Party-ID: "Sam" <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Seam" <sip:[email protected]>;tag=CEF37490-172C
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 14:45:47 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 3989446920-1171263969-2466545983-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327416347
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 2438 9821 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 19412 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
103004: Jan 24 14:45:47.354: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 404 Not Found
From: "Sam "<sip:[email protected]>;tag=CEF37490-172C
To: <sip:[email protected]>;tag=7fad61f03708-100007f-13c4-55013-a0142-10fd12c8-a0142
Call-ID: [email protected]
CSeq: 101 INVITE
Via: SIP/2.0/UDP 10.1.1.101:5060;received=88.99.77.44;branch=z9hG4bK4875CB9
Content-Length: 0
103005: Jan 24 14:45:47.362: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK4875CB9
From: "Sam " <sip:[email protected]>;tag=CEF37490-172C
To: <sip:[email protected]>;tag=7fad61f03708-100007f-13c4-55013-a0142-10fd12c8-a0142
Date: Tue, 24 Jan 2012 14:45:47 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0
103006: Jan 24 14:45:47.374: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/1, TEI 96 changed to up
103007: Jan 24 14:45:51.313: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=211, Peer Info Type=DIALPEER_INFO_SPEECH
103008: Jan 24 14:45:51.313: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=211
103009: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
103010: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=20018
103011: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=0862157774, Peer Info Type=DIALPEER_INFO_SPEECH
103012: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=0862157774
103013: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
103014: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
   Result=NO_MATCH(-1)
103015: Jan 24 14:46:08.815: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/1, TEI 96 changed to down
2801(config-dial-peer)#
Then I removed SIP-UA as I was told there is no registration necessary, only Dial-peer configuration.
But it didn’t affect anything.
Then I add translate-outgoing called 10 command to dial-peer 9000, nothing happened.
Really stuck and don't know where to look at.
Any help will be highly appreciated.
Thanks.

Hi Dan.
Yes, I saw that RTP debugging, but what can I change there? Maybe I need to open more ports on ASA for RTP like 19412?
I use Cisco ASDM for ASA to make changes.
There are static NAT rules for: Server source IPs(10.1.1.100) to Outside(translated IPs, 88.99.77.44) for a few ports.
Also I added Security policy access rules for LAN: Any to SIP, and Outside: SIP to any.
For NAT:
I can't add this: for LAN: STATIC ROUTER IP 10.1.1.101 (AS SOURCE) UDP 5060 TO OUTSIDE IP 88.99.77.44
(AS TRANSLATED) UDP 5060
Because there is already translation for the Server.
Debugging looks like that now. There is no Received: SIP/2.0, but I can make an outside call with no audio.
116013: Jan 25 15:28:25.584: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=90862157774, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
116014: Jan 25 15:28:25.584: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=9000
116015: Jan 25 15:28:25.584: //-1/0D0EB9CE9708/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
116016: Jan 25 15:28:25.584: //-1/0D0EB9CE9708/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=90862157774
116017: Jan 25 15:28:25.584: //-1/0D0EB9CE9708/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
116018: Jan 25 15:28:25.584: //-1/0D0EB9CE9708/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=9000
     2: Dial-peer Tag=2
     3: Dial-peer Tag=1
116019: Jan 25 15:28:25.588: fb_get_reject_cause_code: ERROR cause_code NULL
116020: Jan 25 15:28:25.600: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK491484D
Remote-Party-ID: "Sam " ;party=calling;screen=no;privacy=off
From: "Sam " ;tag=D4410748-1C9D
To:
Date: Wed, 25 Jan 2012 15:28:25 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 219068878-1184895457-2533916991-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327505305
Contact:
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 1984 5803 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 18782 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
116021: Jan 25 15:28:26.096: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK491484D
Remote-Party-ID: "Sam " ;party=calling;screen=no;privacy=off
From: "Sam " ;tag=D4410748-1C9D
To:
Date: Wed, 25 Jan 2012 15:28:26 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 219068878-1184895457-2533916991-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327505306
Contact:
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 1984 5803 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 18782 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
116022: Jan 25 15:28:27.096: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK491484D
Remote-Party-ID: "Sam " ;party=calling;screen=no;privacy=off
From: "Sam " ;tag=D4410748-1C9D
To:
Date: Wed, 25 Jan 2012 15:28:27 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 219068878-1184895457-2533916991-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327505307
Contact:
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 1984 5803 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 18782 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
116026: Jan 25 15:28:57.092: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK491484D
Remote-Party-ID: "Sam" ;party=calling;screen=no;privacy=off
From: "Sam " ;tag=D4410748-1C9D
To:
Date: Wed, 25 Jan 2012 15:28:57 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 219068878-1184895457-2533916991-1958389preference 1771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327505337
Contact:
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 1984 5803 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 18782 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
I'll add Incoming dial-peer now.
Not sure what kind of NAT rule should I put into ASA to allow in and out sip traffic.
Appretiate your help.
Thanks a mill.

Cisco Jabber for Mac 9.2.1: slow to register with CUCM

Hi,
We have this specific problem on our Jabber for Mac 9.2.1 client only: the client takes 60 to 70 seconds to connect to CUCM (running 8.6.2) when it starts.
After Jabber registers with CUCM, there is no issue, it's just very slow to register.
Anybody getting the same behaviour? We have no such issue on previous versions of Jabber for Mac version 8 or Jabber for Windows version 9.
Thanks,
Fabrice

For those interested, I have the answer to my own question: if one of your configured DNS servers is not responding, Jabber 9.2.1 will delay registration to the phone services. This behaviour is seen only in this specifc version of Jabber, hopefully it will be fixed in the next release. Watch out if one of your DNS server goes offilne.
Fabrice

Slow JDBC calls with wrong configured DNS

Similar Messages

Maybe you are looking for