Template:SIP Profile Test RINGING no: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Ringing is not signalled by the provider. This will lead to incorrect call-state display on the PBX (phone-UI, myPBX, Soap) for outbound calls to the PSTN. The caller will see no status-update on the phone-display/PC-screen, showing that the remote party was reached and is ringing. | Ringing is not signalled by the provider. This will lead to incorrect call-state display on the PBX (phone-UI, myPBX, Soap) for outbound calls to the PSTN. The caller will see no status-update on the phone-display/PC-screen, showing that the remote party was reached and is ringing. | ||
: Additionally external callers forwarded/transferred back to the PSTN, may get no ring-tone but hear silence while the remote party is ringing. This silence while waiting might lead to aborting the call. As a result, 'Carrier w/o Alerting' is required in all PBX 'Mobility' objects. | : Additionally external callers forwarded/transferred back to the PSTN, may get no ring-tone but hear silence while the remote party is ringing. This silence while waiting might lead to aborting the call. As a result, ''Carrier w/o Alerting'' is required in all PBX 'Mobility' objects. | ||
Latest revision as of 13:54, 30 June 2017
Ringing is not signalled by the provider. This will lead to incorrect call-state display on the PBX (phone-UI, myPBX, Soap) for outbound calls to the PSTN. The caller will see no status-update on the phone-display/PC-screen, showing that the remote party was reached and is ringing.
- Additionally external callers forwarded/transferred back to the PSTN, may get no ring-tone but hear silence while the remote party is ringing. This silence while waiting might lead to aborting the call. As a result, Carrier w/o Alerting is required in all PBX 'Mobility' objects.