Messages

1

Yate bugs / Re: interoperability with Ericsson SIP-stack

« on: February 06, 2013, 04:33:49 AM »

85.90.74.40 is Yate
84.35.246.21 is SIP-gateway

2

Yate bugs / interoperability with Ericsson SIP-stack

« on: February 05, 2013, 02:03:04 AM »

Hello,

using Yate 4.2.0 2
mandriva kernel (version 2.6.33.7-server-2mnb)


Call is transited to PSTN which causes 183 session progress to be sent back to Ericsson SIP-server including SDP.
When PSTN destination answers, 200OK including SDP is sent again towards Ericsson SIP-server.
The contents of the session version parameter in the 200OK is incremented by 1 for SDP content which
is unchanged. This causes Ericsson SIP stack to release the call directly.

RFC2327 says the following:
.. <version> is a version number for this announcement. It is needed for proxy announcements to detect which of several announcements for the same session is the most recent. Again its usage is up to the creating tool, so long as <version> is increased when a modification is made to the session data. Again, it is recommended (but not mandatory) that an NTP timestamp is used.

RFC3264 says the following:
If the version in the origin line does not increment, the SDP MUST be identical to the SDP with that version number. The answerer MUST be prepared to receive an offer that contains SDP with a version that has not changed; this is effectively a no-op. However, the answerer MUST generate a valid answer (which MAY be the same as the previous SDP from the answerer, or MAY be different), according to the procedures defined in Section

Some discoussions about this were seen on yate Mailing Archive but withouth an answer
http://yate.null.ro/archive/?action=show_msg&actionargs[]=57&actionargs[]=73

My question is it possible to have Yate RFC3264 complaint and let Yate send and answer that contains a SDP with a version that has not been changed?

Thanks,
Martin

3

Yate bugs / Re: transcoding from A-law to u-law not working

« on: November 23, 2012, 04:14:38 AM »

I made the following changes in ysipchan.conf but withouth sucess

[codecs]
default=disable

;mulaw=default
mulaw=enable

;alaw=default
alaw=enable

1xx_change_formats=yes


Any idea what is wrong?

Thanks in advance,
Martin Savelsberg

4

Yate bugs / transcoding from A-law to u-law not working

« on: November 22, 2012, 01:41:29 PM »

Hello,

using Yate 4.2.0 2
mandriva kernel (version 2.6.33.7-server-2mnb)

registered customer is using codec g711 alaw for making calls. We want Yate to transcode this to g711 ulaw for outgoing calls

We added the following lines to regexroute.conf

[default]
${rtp_forward}possible=;rtp_forward=yes
${rtp_forward}^yes$^=;formats=${oformats}
${formats}^=;formats=mulaw

The problem is that transcoding is not working, as calls going out of Yate are still with g711 alaw

In yate log I see "  'alaw' -> [0x7fa250019150] 'alaw' succeeded  "

in the attachment I added the complete log of a call attempt.

Any idea what I'm missing in the config ?

Thanks in advance
Martin Savelsberg