--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/f3d71a79-251d-4db8-8b39-ebc1d0cc6369%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
CSIPSimple working and not the Polycom pretty much confirms that this is a UA issue. Forked early media is basically two or more 183 (with SDP) coming from different endpoints. They convey two or more distinct streams. Polycom is known to work well with forks but I am not really sure if there is a known issue with forked calls with multiple early media. Perhaps a firmware upgrade is in order and see if things improve.
On Tue, Mar 13, 2018 at 10:14 PM, <cmasc...@gmail.com> wrote:
Posting in a new thread because all of my posts to the original thread are getting deleted. ???
If by 'calling UA' you mean the endpoint placing the call, it's a Polycom SoundPoint IP 450, firmware 4.0.12.
I just tried the same thing with a different endpoint: CSipSimple 1.02.03 r2469: inbound media OK!
I repeated the test with the Polycom: no inbound media.
All endpoints and sipXcom are on the same LAN.
SIP signalling does have early media (183 response).
I must be missing something, because the SIP signalling between sipXcom and the endpoint looks the same to me for the 1-trunk case (no trunk failover) and the 2-trunk case. I don't see how the endpoint knows the difference between the two cases, so I don't understand why the Polycom works in the 1-trunk case but not in the 2-trunk case.
What is a forked early media stream?
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/a85065cd-b803-4ebc-8d5b-6c177c3921c0%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/3fe568cb-b4cb-47c5-81a9-bdcad35ea76f%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/00835bde-66f6-4745-9f42-a882ab18660d%40googlegroups.com.