Hey Guys,
Is it mandatory for SIP servers to generate to UA 180 Ringing to inform them that the called party is now ringing ?
The reason i'm asking is because I am seeing strange results using different UAs.
Using SIP clients to call out , instead of seeing 180 Ringing , i see 183 session progress even before call was picked up.
On some sip client , ring back can be heard. On some others , ring back cannot be heard.
Is there any reason to suspect that these UAs needs to receive 180 Ringing before generating any ringback ?
Regards, Sam
Hi Sam,
* Sam Lee sam.lee@super.net.sg [070206 11:09]:
Hey Guys,
Is it mandatory for SIP servers to generate to UA 180 Ringing to inform them that the called party is now ringing ?
No
The reason i'm asking is because I am seeing strange results using different UAs.
Using SIP clients to call out , instead of seeing 180 Ringing , i see 183 session progress even before call was picked up.
This is nothing wrong with this :)
On some sip client , ring back can be heard.
good, they support early media
On some others , ring back cannot be heard.
Bad,, they do not support Early media
Is there any reason to suspect that these UAs needs to receive 180 Ringing before generating any ringback ?
In general: 180 == Generate Local Ringback. 183 == get RTP from callee, and play it (often used for network announcements, calls to gSM and simular)
- Atle
Regards, Sam
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Also note that on ISDN/SIP gateways, you often have many options to fine-tune this. Like progress indicators mappings, play local tone or just forward distant, etc.
On Tue, 2007-02-06 at 11:17 +0100, Atle Samuelsen wrote:
Hi Sam,
- Sam Lee sam.lee@super.net.sg [070206 11:09]:
Hey Guys,
Is it mandatory for SIP servers to generate to UA 180 Ringing to inform them that the called party is now ringing ?
No
The reason i'm asking is because I am seeing strange results using different UAs.
Using SIP clients to call out , instead of seeing 180 Ringing , i see 183 session progress even before call was picked up.
This is nothing wrong with this :)
On some sip client , ring back can be heard.
good, they support early media
On some others , ring back cannot be heard.
Bad,, they do not support Early media
Is there any reason to suspect that these UAs needs to receive 180 Ringing before generating any ringback ?
In general: 180 == Generate Local Ringback. 183 == get RTP from callee, and play it (often used for network announcements, calls to gSM and simular)
- Atle
Regards, Sam
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
And it is also common that a gateway sends both - 180 (ISDN Alerting) and 183 (ISDN Progress with inband audio available)
regards klaus
Jerome Martin wrote:
Also note that on ISDN/SIP gateways, you often have many options to fine-tune this. Like progress indicators mappings, play local tone or just forward distant, etc.
On Tue, 2007-02-06 at 11:17 +0100, Atle Samuelsen wrote:
Hi Sam,
- Sam Lee sam.lee@super.net.sg [070206 11:09]:
Hey Guys,
Is it mandatory for SIP servers to generate to UA 180 Ringing to inform them that the called party is now ringing ?
No
The reason i'm asking is because I am seeing strange results using different UAs.
Using SIP clients to call out , instead of seeing 180 Ringing , i see 183 session progress even before call was picked up.
This is nothing wrong with this :)
On some sip client , ring back can be heard.
good, they support early media
On some others , ring back cannot be heard.
Bad,, they do not support Early media
Is there any reason to suspect that these UAs needs to receive 180 Ringing before generating any ringback ?
In general: 180 == Generate Local Ringback. 183 == get RTP from callee, and play it (often used for network announcements, calls to gSM and simular)
- Atle
Regards, Sam _______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi
* Klaus Darilion klaus.mailinglists@pernau.at [070206 13:56]:
And it is also common that a gateway sends both - 180 (ISDN Alerting) and 183 (ISDN Progress with inband audio available)
note: CAN send both :)
- Atle
regards klaus
Jerome Martin wrote:
Also note that on ISDN/SIP gateways, you often have many options to fine-tune this. Like progress indicators mappings, play local tone or just forward distant, etc. On Tue, 2007-02-06 at 11:17 +0100, Atle Samuelsen wrote:
Hi Sam,
- Sam Lee sam.lee@super.net.sg [070206 11:09]:
Hey Guys, Is it mandatory for SIP servers to generate to UA 180 Ringing to inform them that the called party is now ringing ?
No
The reason i'm asking is because I am seeing strange results using different UAs. Using SIP clients to call out , instead of seeing 180 Ringing , i see 183 session progress even before call was picked up.
This is nothing wrong with this :)
On some sip client , ring back can be heard.
good, they support early media
On some others , ring back cannot be heard.
Bad,, they do not support Early media
Is there any reason to suspect that these UAs needs to receive 180 Ringing before generating any ringback ?
In general: 180 == Generate Local Ringback. 183 == get RTP from callee, and play it (often used for network announcements, calls to gSM and simular)
- Atle
Regards, Sam _______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-- Klaus Darilion nic.at
Atle Samuelsen wrote:
Hi
- Klaus Darilion klaus.mailinglists@pernau.at [070206 13:56]:
And it is also common that a gateway sends both - 180 (ISDN Alerting) and 183 (ISDN Progress with inband audio available)
note: CAN send both :)
What is CAN?
Hmm. I tried tweaking the Progress Indic. Doesn't help much. I read the tech notes for the gateway. They don't seem to generate 180 Ringing at all. All call flows shows only 183 Session Progress.
-----Original Message----- From: Jerome Martin [mailto:jmartin@longphone.fr] Sent: Tuesday, February 06, 2007 7:07 PM To: Atle Samuelsen Cc: Sam Lee; users@openser.org Subject: Re: [Users] 180 Ringing / 183 Session Progress
Also note that on ISDN/SIP gateways, you often have many options to fine-tune this. Like progress indicators mappings, play local tone or just forward distant, etc.
On Tue, 2007-02-06 at 11:17 +0100, Atle Samuelsen wrote:
Hi Sam,
- Sam Lee sam.lee@super.net.sg [070206 11:09]:
Hey Guys,
Is it mandatory for SIP servers to generate to UA 180 Ringing to inform them that the called party is now ringing ?
No
The reason i'm asking is because I am seeing strange results using different UAs.
Using SIP clients to call out , instead of seeing 180 Ringing , i see 183 session progress even before call was picked up.
This is nothing wrong with this :)
On some sip client , ring back can be heard.
good, they support early media
On some others , ring back cannot be heard.
Bad,, they do not support Early media
Is there any reason to suspect that these UAs needs to receive 180 Ringing before generating any ringback ?
In general: 180 == Generate Local Ringback. 183 == get RTP from callee, and play it (often used for network announcements, calls to gSM and simular)
- Atle
Regards, Sam
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Atle Samuelsen -
Jerome Martin -
Klaus Darilion -
Sam Lee