-
Bonjour, trames g729 et transfert n'ont rien avoir avec.
Je vous invite de tout simplement effectuer un debug sip pour savoir pourquoi " l'appel abouti (pas toujours) "
-
Copie du SIP Debug
Bonjour,
Comme demandé, voici le SIP debug que j'ai réalisé à la suite d'un transfert automatique:
IXDPG425*CLI>
<--- SIP read from 91.121.129.17:5060 --->
BYE sip:0033972144916@86.67.22.248:8088 SIP/2.0
Call-ID: 31645-TR-059bfaf8-352e602d4@sip.ovh.net
CSeq: 93991000 BYE
From: "Fabrice" <sip:0972218214@sip.ovh.net;user=phone>;tag=3164 5-RU-059bfaf9-78
9738fb6
Max-Forwards: 29
Reason: q.850;cause=16
To: <sip:0972144916@91.121.129.17;user=phone>;tag=as24 be9371
User-Agent: Cirpack/v4.42q (gw_sip)
Via: SIP/2.0/UDP 91.121.129.17:5060;branch=z9hG4bK-50B1-2D4BC9
Content-Length: 0
<------------->
--- (10 headers 0 lines) ---
Sending to 91.121.129.17 : 5060 (no NAT)
<--- Transmitting (no NAT-SendResponse) to 91.121.129.17:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.129.17:5060;branch=z9hG4bK-50B1-2D4BC9;received=91.121.1
29.17
From: "Fabrice" <sip:0972218214@sip.ovh.net;user=phone>;tag=3164 5-RU-059bfaf9-78
9738fb6
To: <sip:0972144916@91.121.129.17;user=phone>;tag=as24 be9371
Call-ID: 31645-TR-059bfaf8-352e602d4@sip.ovh.net
CSeq: 93991000 BYE
User-Agent: IP-PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:0033972144916@86.67.22.248:8088>
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '1743cd6d27324aad69c7da9e4a90c829@sip.ovh.n
et' in 32000 ms (Method: ACK)
set_destination: Parsing <sip:91.121.129.17:5060> for address/port to send to
set_destination: set destination to 91.121.129.17, port 5060
Reliably Transmitting (no NAT-SendRequest) to 91.121.129.17:5060:
BYE sip:91.121.129.17:5060 SIP/2.0
Via: SIP/2.0/UDP 86.67.22.248:8088;branch=z9hG4bK3ef2bdf5;rport
From: "Fabrice" <sip:0972144916@sip.ovh.net>;tag=as3770d88b
To: <sip:0169909185@sip.ovh.net>;tag=00-07929-059bfb26-03c7b84e3
Call-ID: 1743cd6d27324aad69c7da9e4a90c829@sip.ovh.net
CSeq: 104 BYE
User-Agent: IP-PBX
Max-Forwards: 70
Proxy-Authorization: Digest username="0972144916", realm="sip.ovh.net", algorith
m=MD5, uri="sip:91.121.129.17:5060", nonce="059bf5047b2f921d378fad34509d353c", r
esponse="42424e4538bab297065e6ebc417a1d47", opaque="0598548f3549f57"
Content-Length: 0
---
IXDPG425*CLI>
<--- SIP read from 91.121.129.17:5060 --->
SIP/2.0 200 OK
Call-ID: 1743cd6d27324aad69c7da9e4a90c829@sip.ovh.net
CSeq: 104 BYE
From: "Fabrice" <sip:0972144916@sip.ovh.net>;tag=as3770d88b
Server: Cirpack/v4.42q (gw_sip)
To: <sip:0169909185@sip.ovh.net>;tag=00-07929-059bfb26-03c7b84e3
Via: SIP/2.0/UDP 86.67.22.248:8088;received=86.67.22.248;rport=8088 ;branch=z9hG4
bK3ef2bdf5
Content-Length: 0
<------------->
--- (8 headers 0 lines) ---
SIP Response message for INCOMING dialog BYE arrived
Really destroying SIP dialog '1743cd6d27324aad69c7da9e4a90c829@sip.ovh.net' Meth
od: ACK
Really destroying SIP dialog '31645-TR-059bfaf8-352e602d4@sip.ovh.net' Method: B
YE
IXDPG425*CLI>
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
Si quelqu'un avait une idée. Pour m'aider à régler ce problème.
-
On voit juste un raccroché ici. Il manque 90% de debug.
-
Sip Debug
Je pense que là l'appel est complet.
IXDPG425*CLI>
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI>
<--- SIP read from 91.121.129.17:5060 --->
BYE sip:0972144916@86.67.22.248:8088 SIP/2.0
Call-ID: 52f473db10284c895c7dccff1d0a19da@sip.ovh.net
CSeq: 95496341 BYE
From: <sip:0169909185@sip.ovh.net>;tag=00-08129-05b31cc7-68eefbd51
Max-Forwards: 31
Reason: q.850;cause=16
To: "0178658779" <sip:0972144916@sip.ovh.net>;tag=as7db46edb
User-Agent: Cirpack/v4.42q (gw_sip)
Via: SIP/2.0/UDP 91.121.129.17:5060;branch=z9hG4bK-439E-2FE4C6
Content-Length: 0
<------------->
--- (10 headers 0 lines) ---
Sending to 91.121.129.17 : 5060 (no NAT)
<--- Transmitting (no NAT-SendResponse) to 91.121.129.17:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.129.17:5060;branch=z9hG4bK-439E-2FE4C6;received=91.121.1
29.17
From: <sip:0169909185@sip.ovh.net>;tag=00-08129-05b31cc7-68eefbd51
To: "0178658779" <sip:0972144916@sip.ovh.net>;tag=as7db46edb
Call-ID: 52f473db10284c895c7dccff1d0a19da@sip.ovh.net
CSeq: 95496341 BYE
User-Agent: IP-PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:0972144916@86.67.22.248:8088>
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '19209-MF-05b31c9e-380c499d3@sip.ovh.net' i
n 32000 ms (Method: ACK)
set_destination: Parsing <sip:91.121.129.17:5060> for address/port to send to
set_destination: set destination to 91.121.129.17, port 5060
Reliably Transmitting (no NAT-SendRequest) to 91.121.129.17:5060:
BYE sip:91.121.129.17:5060 SIP/2.0
Via: SIP/2.0/UDP 86.67.22.248:8088;branch=z9hG4bK0383902e;rport
From: <sip:0972144916@91.121.129.17;user=phone>;tag=as5f d43a18
To: "0178658779" <sip:0178658779@sip.ovh.net;user=phone>;tag=1920 9-JN-05b31c9f-2
5ffbb292
Call-ID: 19209-MF-05b31c9e-380c499d3@sip.ovh.net
CSeq: 102 BYE
User-Agent: IP-PBX
Max-Forwards: 70
Content-Length: 0
---
IXDPG425*CLI>
<--- SIP read from 91.121.129.17:5060 --->
SIP/2.0 200 OK
Call-ID: 19209-MF-05b31c9e-380c499d3@sip.ovh.net
CSeq: 102 BYE
From: <sip:0972144916@91.121.129.17;user=phone>;tag=as5f d43a18
Server: Cirpack/v4.42q (gw_sip)
To: "0178658779" <sip:0178658779@sip.ovh.net;user=phone>;tag=1920 9-JN-05b31c9f-2
5ffbb292
Via: SIP/2.0/UDP 86.67.22.248:8088;received=86.67.22.248;rport=8088 ;branch=z9hG4
bK0383902e
Content-Length: 0
<------------->
--- (8 headers 0 lines) ---
SIP Response message for INCOMING dialog BYE arrived
Really destroying SIP dialog '52f473db10284c895c7dccff1d0a19da@sip.ovh.net' Meth
od: BYE
Really destroying SIP dialog '19209-MF-05b31c9e-380c499d3@sip.ovh.net' Method: A
CK
Really destroying SIP dialog '5f97424c4ab0ac273bdd72c0513ea623@127.0.0.1' Method
: REGISTER
Really destroying SIP dialog '462f5ba66a148fda0d86ff970291abdf@127.0.0.1' Method
: REGISTER
IXDPG425*CLI>
<--- SIP read from 192.168.1.9:5062 --->
<------------->
--- (0 headers 1 lines) ---
IXDPG425*CLI>
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI>
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> help
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> help
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> help
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> help
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> help
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> help
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> help
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> sip set debug off
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> sip set debug off
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> sip set debug off
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> sip set debug off
<--- SIP read from 91.121.129.17:5060 --->
Cirpack KeepAlive Packet
<------------->
--- (1 headers 0 lines) ---
IXDPG425*CLI> sip set debug off
SIP Debugging Disabled
IXDPG425*CLI>
-
SIP Debug
Voici le fichier joint avec la totalité du SIP Débug.
Si quelqu'un avait une idée pour mon probléme.
MerciCAPTURE.zip
-
Ton serveur est en publique ?
-
Pas compris
Je ne comprend pas ta question.
Règles de messages
- Vous ne pouvez pas créer de nouvelles discussions
- Vous ne pouvez pas envoyer des réponses
- Vous ne pouvez pas envoyer des pièces jointes
- Vous ne pouvez pas modifier vos messages
-
Règles du forum