thr3ads.net - asterisk users - [Asterisk-Users] one outgoing call == one call per minute [Nov 2005]

If this information is useful, please help other people find it:
Share via:

Brian May

2005-Nov-10 23:24 UTC

[Asterisk-Users] one outgoing call == one call per minute

Hello,

I am just in the process of getting asterisk connected to an
egin VOIP account in Australia.

What works:
* ALL incomming calls.
* outgoing calls from Zap interface.

What almost works:
* outgoing calls from Sipura/SPA2100-3.2.1 (eth0) via Asterisk to Egin
  (eth1).

At first it appears to work perfectly - sound works in both directions,
etc.

After approx one minute, what happens depends on the remote phone:

* if voice mail, the Sipura caller gets transferred to voice mail.

* the person at the remote end gets call waiting,
  and finds the original caller again. The first call is a dead (not
  hung up) connection.

Its almost like the first caller pushed recall, and redialed the
number again, but the first caller can hear the second caller's original
call, but not vice-versa. This is hard to hear though, since the second
caller is usually trying to say "hello? hELLOOOO?" in competition with
the voicemail message.

At the point the problem occured my brother hang up the sipura phone,
and contacted me on extension 6003 (as seen in attached log files for
eth0).

I have attached tethreal logs on eth0 (Sipura to asterisk) and eth1
(asterisk to egin).

It would appear that asterisk is generating an extra INVITE command on eth1.
Why???

I don't see any similar INVITE command on eth0.

I also see "SIP Status: 481 Call/Transaction Does Not Exist" errors -
but this happens after the extra INVITE so I think it is another symptom
of the problem as opposed to the problem itself.

Disclaimer: I am expert on the SIP protocol...
-- 
Brian May <bam@snoopy.apana.org.au>
-------------- next part --------------
  0.000000 192.168.87.70 -> 192.168.87.1 SIP/SDP Request: INVITE
sip:90419503953@192.168.87.1, with session description
  0.000518 192.168.87.1 -> 192.168.87.70 SIP Status: 407 Proxy Authentication
Required
  0.007510 192.168.87.70 -> 192.168.87.1 SIP Request: ACK
sip:90419503953@192.168.87.1
  0.011840 192.168.87.70 -> 192.168.87.1 SIP/SDP Request: INVITE
sip:90419503953@192.168.87.1, with session description
  0.012223 192.168.87.1 -> 192.168.87.70 SIP Status: 100 Trying
  6.346837 192.168.87.1 -> 192.168.87.70 SIP/SDP Status: 183 Session
Progress, with session description
  8.067548 192.168.87.1 -> 192.168.87.70 SIP/SDP Status: 200 OK, with session
description
  8.078536 192.168.87.70 -> 192.168.87.1 SIP Request: ACK
sip:90419503953@192.168.87.1
  8.078722 192.168.87.1 -> 192.168.87.70 SIP/SDP Request: INVITE
sip:phillip@192.168.87.70:5061, with session description
  8.090110 192.168.87.70 -> 192.168.87.1 SIP/SDP Status: 200 OK, with session
description
  8.090276 192.168.87.1 -> 192.168.87.70 SIP Request: ACK
sip:phillip@192.168.87.70:5061
 49.294879 192.168.87.1 -> 192.168.87.70 SIP/SDP Request: INVITE
sip:phillip@192.168.87.70:5061, with session description
 49.309931 192.168.87.70 -> 192.168.87.1 SIP/SDP Status: 200 OK, with session
description
 49.310156 192.168.87.1 -> 192.168.87.70 SIP Request: ACK
sip:phillip@192.168.87.70:5061
 54.985854 192.168.87.70 -> 192.168.87.1 SIP Request: BYE
sip:90419503953@192.168.87.1
 54.986054 192.168.87.1 -> 192.168.87.70 SIP Status: 200 OK
 57.518254 192.168.87.70 -> 192.168.87.1 SIP/SDP Request: INVITE
sip:6003@192.168.87.1, with session description
 57.518737 192.168.87.1 -> 192.168.87.70 SIP Status: 407 Proxy Authentication
Required
 57.526203 192.168.87.70 -> 192.168.87.1 SIP Request: ACK
sip:6003@192.168.87.1
 57.530554 192.168.87.70 -> 192.168.87.1 SIP/SDP Request: INVITE
sip:6003@192.168.87.1, with session description
 57.530882 192.168.87.1 -> 192.168.87.70 SIP Status: 100 Trying
 57.553155 192.168.87.1 -> 192.168.87.70 SIP Status: 180 Ringing
 60.473068 192.168.87.1 -> 192.168.87.70 SIP/SDP Status: 200 OK, with session
description
 60.487031 192.168.87.70 -> 192.168.87.1 SIP Request: ACK
sip:6003@192.168.87.1
 64.044937 192.168.87.70 -> 192.168.87.1 SIP Request: BYE
sip:6003@192.168.87.1
 64.045068 192.168.87.1 -> 192.168.87.70 SIP Status: 200 OK
-------------- next part --------------
  0.000000 202.173.153.89 -> 202.61.13.40 SIP Request: REGISTER
sip:byo.engin.com.au
  0.037776 202.61.13.40 -> 202.173.153.89 SIP Status: 200 OK    (1 bindings)
 11.341364 202.173.153.89 -> 202.61.13.40 SIP/SDP Request: INVITE
sip:0419503953@byo.engin.com.au, with session description
 11.377687 202.61.13.40 -> 202.173.153.89 SIP Status: 100 Trying
 11.450946 202.61.13.40 -> 202.173.153.89 SIP Status: 407 Proxy
Authentication Required
 11.451144 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:0419503953@byo.engin.com.au
 11.451315 202.173.153.89 -> 202.61.13.40 SIP/SDP Request: INVITE
sip:0419503953@byo.engin.com.au, with session description
 11.507928 202.61.13.40 -> 202.173.153.89 SIP Status: 100 Trying
 17.675080 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 183 Session
Progress, with session description
 19.395642 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 19.395894 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:0419503953@byo.engin.com.au
 19.396328 202.173.153.89 -> 202.61.13.40 SIP/SDP Request: INVITE
sip:FNGdju7sPUBrV0ap7AoWzd1D1imMjsVbj8OaReO@202.61.13.40:5060, with session
description
 19.517816 202.61.13.40 -> 202.173.153.89 SIP Status: 407 Proxy
Authentication Required
 19.518031 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:FNGdju7sPUBrV0ap7AoWzd1D1imMjsVbj8OaReO@202.61.13.40:5060
 19.518220 202.173.153.89 -> 202.61.13.40 SIP/SDP Request: INVITE
sip:0419503953@byo.engin.com.au, with session description
 19.570627 202.61.13.40 -> 202.173.153.89 SIP Status: 100 Trying
 40.076777 202.173.153.89 -> 202.61.13.40 SIP Request: REGISTER
sip:byo.engin.com.au
 40.110195 202.61.13.40 -> 202.173.153.89 SIP Status: 200 OK    (1 bindings)
 59.029129 202.61.13.40 -> 202.173.153.89 SIP Status: 180 Ringing
 60.622984 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 60.623303 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:FNGdju7sPUBrV0ap7AoWzd1D1imMjsVbj8OaReO@202.61.13.40:5060
 61.126107 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 61.126416 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:FNGdju7sPUBrV0ap7AoWzd1D1imMjsVbj8OaReO@202.61.13.40:5060
 62.203513 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 62.203767 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:FNGdju7sPUBrV0ap7AoWzd1D1imMjsVbj8OaReO@202.61.13.40:5060
 64.119379 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 64.119651 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:FNGdju7sPUBrV0ap7AoWzd1D1imMjsVbj8OaReO@202.61.13.40:5060
 66.314915 202.173.153.89 -> 202.61.13.40 SIP/SDP Request: INVITE
sip:AWe97o6MXSALNybJjGp2rb1D1imMjsVbj8OaReO@202.61.13.40:5060, with session
description
 66.432663 202.61.13.40 -> 202.173.153.89 SIP Status: 407 Proxy
Authentication Required
 66.432991 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:AWe97o6MXSALNybJjGp2rb1D1imMjsVbj8OaReO@202.61.13.40:5060
 66.433170 202.173.153.89 -> 202.61.13.40 SIP/SDP Request: INVITE
sip:0419503953@byo.engin.com.au, with session description
 66.483646 202.61.13.40 -> 202.173.153.89 SIP Status: 100 Trying
 68.121976 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 68.122251 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:AWe97o6MXSALNybJjGp2rb1D1imMjsVbj8OaReO@202.61.13.40:5060
 68.122360 202.173.153.89 -> 202.61.13.40 SIP Request: BYE
sip:AWe97o6MXSALNybJjGp2rb1D1imMjsVbj8OaReO@202.61.13.40:5060
 68.198598 202.61.13.40 -> 202.173.153.89 SIP Status: 200 OK
 72.121839 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 72.122105 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:AWe97o6MXSALNybJjGp2rb1D1imMjsVbj8OaReO@202.61.13.40:5060
 72.122212 202.173.153.89 -> 202.61.13.40 SIP Request: BYE
sip:AWe97o6MXSALNybJjGp2rb1D1imMjsVbj8OaReO@202.61.13.40:5060
 72.172215 202.61.13.40 -> 202.173.153.89 SIP Status: 481 Call/Transaction
Does Not Exist
 75.069890 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 183 Session
Progress, with session description
 76.119477 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 76.119786 202.173.153.89 -> 202.61.13.40 SIP Request: ACK
sip:AWe97o6MXSALNybJjGp2rb1D1imMjsVbj8OaReO@202.61.13.40:5060
 76.119896 202.173.153.89 -> 202.61.13.40 SIP Request: BYE
sip:AWe97o6MXSALNybJjGp2rb1D1imMjsVbj8OaReO@202.61.13.40:5060
 76.172546 202.61.13.40 -> 202.173.153.89 SIP Status: 481 Call/Transaction
Does Not Exist
 80.112544 202.173.153.89 -> 202.61.12.166 SIP Request: REGISTER
sip:byo.engin.com.au
 80.117655 202.61.13.40 -> 202.173.153.89 SIP Request: BYE
sip:0390174985@202.173.153.89
 80.117821 202.173.153.89 -> 202.61.13.40 SIP Status: 200 OK
 80.183008 202.61.12.166 -> 202.173.153.89 SIP Status: 200 OK    (1 bindings)
 80.509424 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 80.509727 202.173.153.89 -> 202.61.13.40 UDP Source port: sip  Destination
port: sip
 80.509838 202.173.153.89 -> 202.61.13.40 SIP Request: BYE
sip:FNGdju7sPUBrV0ap7AoWzd1D1imMjsVbj8OaReO@202.61.13.40:5060
 80.552426 202.61.13.40 -> 202.173.153.89 SIP Status: 481 Call/Transaction
Does Not Exist
 81.000788 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 82.000718 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 84.008377 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 88.015952 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 91.999853 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description
 95.997219 202.61.13.40 -> 202.173.153.89 SIP/SDP Status: 200 OK, with
session description

Brian May

2005-Nov-14 00:48 UTC

head link

[Asterisk-Users] one outgoing call == one call per minute

On Fri, Nov 11, 2005 at 05:24:44PM +1100, Brian May wrote:
...
> At first it appears to work perfectly - sound works in both directions,
> etc.
> 
> After approx one minute, what happens depends on the remote phone:
> 
> * if voice mail, the Sipura caller gets transferred to voice mail.
> 
> * the person at the remote end gets call waiting,
>   and finds the original caller again. The first call is a dead (not
>   hung up) connection.
> 
> Its almost like the first caller pushed recall, and redialed the
> number again, but the first caller can hear the second caller's
original
> call, but not vice-versa. This is hard to hear though, since the second
> caller is usually trying to say "hello? hELLOOOO?" in competition
with
The problem seems to be something to do with reinvite support, if I turn
that off for engin, it seems to work.

Curious. I see some comments that reinvite does not always work via NAT,
but initially it seems to work fine (for the first 40-60 seconds). Oh
well.

At least I got it working now.
-- 
Brian May <bam@snoopy.apana.org.au>

asterisk users - Nov 2005 - one outgoing call == one call per minute

[Asterisk-Users] one outgoing call == one call per minute

[Asterisk-Users] one outgoing call == one call per minute