03-08-2017 09:56 AM - edited 03-17-2019 09:45 AM
Hi,
I have a trunk SIP between a Cisco 2911 router (connected to PSTN via E1) and an Alcatel OXE IPBX.
The IPBX uses a name in SIP message: oxe.test.dom
So locally, in my Cisco 2911 router, i added the command:
ip host oxe.test.dom 192.168.101.2
For incoming calls, coming from PSTN to Cisco 2911 and to IPBX,
While the called phone rings, when we pick up the called phone, the calling phone continues ringing.
When we hang up after the first ring, we always have the issue.
When we hang up the call after 3 rings, we have the issue from time to time.
When i enter "debug ccsip all",
I can check that the IPBX sends to my router the SIP message which confirms that the phone rings:
Received:
SIP/2.0 180 Ringing
and when I hang up the called phone, the IPBX sent to my router the SIP message which confirms the call is hang up
Received:
SIP/2.0 200 OK
Then, when it works, my Cisco router sends immediately the ACK message:
Sent:
ACK sip:oxe.test.dom SIP/2.0
and then , the call is OK
But when it fails, my Cisco 2911 router displays the error message:
Mar 8 11:38:06.541: //1881/6D50C8348393/SIP/Info/critical/8192/sipSPIhandle200OKInvite: Drop 200 OK while DNS query is in progress...
and does not send tha ACK SIP message to the IPBX.
Then, the IPBX sends my router 5 times the SIP messsage:
Received:
SIP/2.0 200 OK
and lastly the IPBX sends my router:
Received:
BYE sip:XXXXXXXXXX@10.100.1.10:5060 SIP/2.0
Do you know if the error message is a BUG ?:
SIP/Info/critical/8192/sipSPIhandle200OKInvite: Drop 200 OK while DNS query is in progress...
Because i found this bug but which is related to CCM and not CIsco 2911 but it seems close to my problem:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCui05612/?referring_site=bugquickviewclick
Conditions:
Using FQDN in the certain fields of a SIP messages, e.g. a host name. If IP address used, there won't have this issue.
Workaround:
Use IP address for a host name.
Thank you
Laurent
03-09-2017 01:47 AM
The issue is fied.
The command
ip host oxe.test.dom 192.168.101.2
was not sufficient.
It was necessary to configure the router as DNS server:
ip dns server
Laurent
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide