This is our old Q&A Site. Please post any new questions and answers at

Hello, I do not the expertise to properly analyze a wireshar log- I hope someone could please help reviewing a WireShark log and find out why a SIP call was dropped: We have an application that uses Dialogic/HMP. This application requests outbound SIP calls to an Asterisk server. Suddenly, our HMP/app receives this message: IPERR_INVALID_PHONE_NUMBER and we have to reboot.

Could someone please, take a quick look ate the Wiresharlog and analyze why and who dropped a particular outbound call? I can supply the log and further info if needed. Thanks a lot

asked 10 Nov '15, 10:04

saveriobaq's gravatar image

accept rate: 0%

Can you upload the packet capture online and post a link? Dropbox for example.

(10 Nov '15, 15:13) Quadratic

Thanks a lot sindy and quadratic. Please download the pcapng file from

Please search from the bottom up for the number I was calling: 60999839104 you will see a 487 Request terminated message. Need to know what happen to this call.

Regards Saverio

(10 Nov '15, 16:38) saveriobaq

OK, I can have a look at the SIP message exchange, but don't expect too much: Wireshark shows you what has happened but not why it has happened. To know why exactly the HMP's SIP stack has dropped the call, you'll need to see its logs, even if I eventually tell you what was wrong with some SIP message.

permanent link

answered 10 Nov '15, 10:11

sindy's gravatar image

accept rate: 24%

I've checked too and I agree with Rooster_50 that there is nothing odd in this particular call as compared to those calls in the capture which have the same calling and called and have not crashed your application.

So as I wrote initially, dive yourself into the HMP's log files which should explain you why HMP has sent to your application the exception (which, I agree, doesn't seem logical in combination with those totally harmless SIP messages).

If you use the HMP together with an E1 card and the SIP calls to Asterisk are triggered by incoming TDM calls, you might want to trace the TDM side simultaneously with running the wireshark to see whether something ugly does not come from the TDM side, as the last step before taking the adventure of reading HMP's logs.

(11 Nov '15, 00:45) sindy

Hi Saverio,
part of your capture is useful to illustrate a Wireshark bug I want to file. I cannot use my own capture which shows the same issue because is taken in production environment at a customer. Would you mind if I use part of your capture to file the bug? It would be the SIP message exchange of the crashed call and the RTP streams which use the same UDP port on the Dialogic side, i.e. the RTP of the crashed call itself and of two other ones.

Thank you

(12 Nov '15, 02:11) sindy

The 487 Request Terminated is in response to the CANCEL request sent by the Client ( terminating the session before a 200 response was received.

The finger is pointed at Check your application logs for further details as to what happened.

permanent link

answered 10 Nov '15, 19:40

Rooster_50's gravatar image

accept rate: 15%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 10 Nov '15, 10:04

question was seen: 2,797 times

last updated: 12 Nov '15, 02:11

p​o​w​e​r​e​d by O​S​Q​A