Difference between revisions of "Troubleshooting RINGING"
(New page: If user complains that he does not hear ringing on his device when call is in progress: 1. Configure your phone with same settings as your users and dial same number 2. Enable sip debug a...) |
|||
| (14 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
If user complains that he does not hear ringing on his device when call is in progress: | If user complains that he does not hear ringing on his device when call is in progress: | ||
1. | 1. [[Why we do not suggest to use IAX2 | Do NOT use IAX2]] - switch to SIP | ||
<--- | 2. Configure your phone with same settings as your users and dial same number | ||
'''SIP/2.0 | If you can hear ringing - advice user to change its device | ||
Via: SIP/2.0/UDP | |||
From: " | More detailed troubleshooting:<br> | ||
To: <sip: | 1. Make call from your Device - get sip debug<br> | ||
Call-ID: | 2. Make call from User's Device - get sip debug<br> | ||
3. Compare debugs, if packets are the same - problem is in User's Device<br> | |||
4. Send sip debugs with comments to the Client and advice to change User's Device<br> | |||
3. Enable sip debug and full log and look for similar message: | |||
<--- SIP read from 193.138.191.205:64439 ---> | |||
'''SIP/2.0 180 Ringing''' | |||
Via: SIP/2.0/UDP 82.19.82.11:5060;branch=z9hG4bK78d3ff31;rport | |||
From: "37068111854" <sip:37068111854@82.19.82.11>;tag=as1f2d0c9d | |||
To: <sip:281@193.138.191.205:5060>;tag=as1f2d0c9d | |||
Contact: <sip:281@193.138.191.205:5060> | |||
Call-ID: 03f6271f1cac11c45d6d47e67245f804@82.19.82.11 | |||
CSeq: 102 INVITE | CSeq: 102 INVITE | ||
User-Agent: | User-Agent: X-PRO build 1082 | ||
Content-Length: 0 | |||
If such message exists that means that callee responds properly and problem is at the other end. | |||
4. If you are dialing over some Provider to DID in MOR and get no ringing, try to change Provider. If it works - that means problem is with Provider #1. | |||
Notice: | |||
If from the provider side no SIP 180 Ringing is received - this means no ringing is generated. | |||
'''MOR Billing does not influence this in any way. Because MOR Billing is not generating ringing at all - it just passes it on if it receives it.''' | |||
The provider for different numbers/destinations can use different routes - this means one route | |||
can be good quality and you have ringing, another one has bad route and no ringing is generated. | |||
5. Make a SIP debug: | |||
If you can see that Provider sends 183 Session in progress to MOR, but MOR sent 180 Ringing to client, please set "Progressin-band" option to "No" on Device and Provider settings. | |||
6. Use [[Fake Ring]] as last resort | |||
<br><br> | |||
= See also = | |||
* http://www.ietf.org/rfc/rfc3960.txt | |||
* http://www.ciscopress.com/articles/article.asp?p=664148 | |||
* http://www.mailfunnel.org/asterisk-users@lists.digium.com/2006-08/msg01260.html | |||
* [[Fake Ring]] | |||
* [[I have a problem with Calls]] | |||
Latest revision as of 06:44, 24 September 2012
If user complains that he does not hear ringing on his device when call is in progress:
1. Do NOT use IAX2 - switch to SIP
2. Configure your phone with same settings as your users and dial same number
If you can hear ringing - advice user to change its device
More detailed troubleshooting:
1. Make call from your Device - get sip debug
2. Make call from User's Device - get sip debug
3. Compare debugs, if packets are the same - problem is in User's Device
4. Send sip debugs with comments to the Client and advice to change User's Device
3. Enable sip debug and full log and look for similar message:
<--- SIP read from 193.138.191.205:64439 ---> SIP/2.0 180 Ringing Via: SIP/2.0/UDP 82.19.82.11:5060;branch=z9hG4bK78d3ff31;rport From: "37068111854" <sip:37068111854@82.19.82.11>;tag=as1f2d0c9d To: <sip:281@193.138.191.205:5060>;tag=as1f2d0c9d Contact: <sip:281@193.138.191.205:5060> Call-ID: 03f6271f1cac11c45d6d47e67245f804@82.19.82.11 CSeq: 102 INVITE User-Agent: X-PRO build 1082 Content-Length: 0
If such message exists that means that callee responds properly and problem is at the other end.
4. If you are dialing over some Provider to DID in MOR and get no ringing, try to change Provider. If it works - that means problem is with Provider #1.
Notice:
If from the provider side no SIP 180 Ringing is received - this means no ringing is generated.
MOR Billing does not influence this in any way. Because MOR Billing is not generating ringing at all - it just passes it on if it receives it.
The provider for different numbers/destinations can use different routes - this means one route
can be good quality and you have ringing, another one has bad route and no ringing is generated.
5. Make a SIP debug:
If you can see that Provider sends 183 Session in progress to MOR, but MOR sent 180 Ringing to client, please set "Progressin-band" option to "No" on Device and Provider settings.
6. Use Fake Ring as last resort
