I have a problem with Snoms occasionally.
From one, lets call it a carrier, we receive a 180, freeswitch then sends this to the Snom endpoint as a 183.
When the 200OK comes in, we get the real audio but there is a significant difference in the sequence number of the rtp packet.
If we use another carrier that sends a 183 we get a nice even spacing of 160 between the rtp packets from the 183 through the 200 etc.
I'm trying to determine if the Snoms are bad, or the freeswitch. I think Yealink fix this up no problem but I'm not sure if thats exactly what they are doing, ie fixing up a problem from elsewhere and this is really a problem that needs fixing at freeswitch
TIA
Daz
From one, lets call it a carrier, we receive a 180, freeswitch then sends this to the Snom endpoint as a 183.
When the 200OK comes in, we get the real audio but there is a significant difference in the sequence number of the rtp packet.
If we use another carrier that sends a 183 we get a nice even spacing of 160 between the rtp packets from the 183 through the 200 etc.
I'm trying to determine if the Snoms are bad, or the freeswitch. I think Yealink fix this up no problem but I'm not sure if thats exactly what they are doing, ie fixing up a problem from elsewhere and this is really a problem that needs fixing at freeswitch
TIA
Daz