Configuring OverSIP for use with my SIP server

[Paan Singh]

Hi, 

I'm trying to run the JS-SIP examples, using OverSIP as the websocket server, which will also talk to another SIP server (not asterisk or kamailio) running on port 5060. Is there a way I can tell OverSIP to relay the connection from the webpage to this SIP server (running on port 5060 ), or do I have this wrong ? 

Thanks ! 

[Iñaki Baz Castillo]

2012/11/26 Paan Singh <paan.sin...@gmail.com>:

Of course, use the Proxy#route method:

http://oversip.net/documentation/1.3.x/api/sip/proxy/



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

[Paan Singh]

Thanks a lot Inaki !  

[MavHood]

Hi,

I have installed overSIP on ubuntu and using Open IMS Core as my server, which accepts requests on pcscf port 4060. So the request from tryit is received  on oversIP and sent to the OSIMS on 5060. And the server responds with SIP/2.0 400 Bad Request - P-Visited-Network-ID header missing.

I have read the documentation from the link above, but not sure how to use that, as i am fairly new to Ruby. Could you give more details how to use this method and where, or can i enter this on a configuration file. Thanks.

Alice

[Iñaki Baz Castillo]

2013/1/10 MavHood <alicem...@googlemail.com>:

> Hi,
> I have installed overSIP on ubuntu and using Open IMS Core as my server,
> which accepts requests on pcscf port 4060. So the request from tryit is
> received on oversIP and sent to the OSIMS on 5060. And the server responds
> with SIP/2.0 400 Bad Request - P-Visited-Network-ID header missing.
>
> I have read the documentation from the link above, but not sure how to use
> that, as i am fairly new to Ruby. Could you give more details how to use
> this method and where, or can i enter this on a configuration file. Thanks.

Open IMS Core is a IMS server so it has IMS requirements including the
presence of the P-Visited-Network-ID header. JsSIP and OverSIP are not
IMS aware (for now) so they won't include such a header.

Anyhow I don't know IMS but I expect that the P-Visited-Network-ID
must be added by the proxy (not sure). If that is the case (check the
IMS documentation) then you can add a header in OverSIP with the
"set_header()" method of OverSIP::SIP::Request class:

http://www.oversip.net/documentation/1.3.x/api/sip/message/

[MavHood]

Ok. Thanks.