Issue with communicating to a sip switchboard

[Daniel Requena Cervantes]

Buenas, 

somos una empresa que queremos integrar una llamada de teléfono mediante
el navegador con javascript usando oversip para comunicarnos con nuestra
centralita, es decir, justo lo que hace oversip. El problema es que
enviamos el primer paquete de REGISTER y nos contesta con un 301 el
servidor sip a oversip.  

Hemos hecho una traza de lo que recibe el servidor SIP con una llamada
de un teléfono que funciona y otra con la nuestra, y lo que vemos
básicamente es que se mandan en la traza de oversip unas cabeceras de
más que no le gusta a nuestra centralita, como por ejemplo Path. La
centralita es innovaphone. ¿Vosotros sabéis cómo se puede configurar las
cabeceras de oversip para intentar tunearla al máximo para que se adapte
a una cabecera para que la centralita sip sí conteste? 

Hemos activado también el modulo outbound_mangling, pero sin éxito. 

Muchas gracias, 

Dani

[Iñaki Baz Castillo]

Hi, this is a mailing list in English language. Please resend your
question in English (and avoid HTML formatted text).

Thanks you.

El día 21 de junio de 2016, 11:14, Daniel Requena Cervantes
<daniel....@gmail.com> escribió:

> --
> You received this message because you are subscribed to the Google Groups
> "OverSIP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to oversip+u...@googlegroups.com.
> To post to this group, send email to ove...@googlegroups.com.
> Visit this group at https://groups.google.com/group/oversip.
> For more options, visit https://groups.google.com/d/optout.



--
Iñaki Baz Castillo
<i...@aliax.net>

[Daniel Requena Cervantes]

Hi,

we want to integrate a phone calling with our navigator using javascript, using oversip to communicate us with our swithboard, this means, the same as does oversip. The problem is that when we send the first packet REGISTER, we always receive the 301 response from sip server to oversip.

We've made a trace to see what's happening with SIP server and with a normal phone calling that works to compare it with the navigator sent data. We see that basically the navigator header sends more data that a normal calling, for example Path. Our switchboard is Innovaphone. Do you what how the oversip headers can ve configurated to avoid this? 

We've enabled the outbound_mangling module, but still doesn't works,

Many thanks,

Dani

--

"El verdadero amor es el amor no correspondido"

[Iñaki Baz Castillo]

2016-06-21 12:01 GMT+02:00 Daniel Requena Cervantes <daniel....@gmail.com>:
> we want to integrate a phone calling with our navigator using javascript,
> using oversip to communicate us with our swithboard, this means, the same as
> does oversip.

Does your swithboard implement WebRTC (this is: ICE, DTLS+SRTP, opus
audio codec, etc)?

If not, things won't work. OverSIP is just a SIP proxy, not a media gateway.

Let's first clarify this important point.