sip-i ?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

sip-i ?

Sean Watkins
Hi

Are there any SIP-I experts on here that are willing todo some consulting?

I need to get a SIP-I to SIP gateway working... I've got partial call
connectivity working, but I don't seem to know what I'm doing..

Don't get all the ins and outs of reply etc..

Sean

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: sip-i ?

Bogdan-Andrei Iancu-2
Hi Sean,

Where have you got stuck ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 2019
   https://www.opensips.org/events/Summit-2019Amsterdam/

On 03/22/2019 10:47 PM, Sean Watkins wrote:

> Hi
>
> Are there any SIP-I experts on here that are willing todo some consulting?
>
> I need to get a SIP-I to SIP gateway working... I've got partial call
> connectivity working, but I don't seem to know what I'm doing..
>
> Don't get all the ins and outs of reply etc..
>
> Sean
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: sip-i ?

Sean Watkins
Hi Bogan

I got some more success yesterday with it --  I'll post my configs
after, for a SIP-I to SIP gateway.

Where I'm stuck now - there seems to be some differences between ANSI
+ ITU. I've got the invite coming into Opensips, then I'm successfully
adding the SDP info for ISUP. (Whomever came up with this... crazy!)

The far end carrier always drops the calls 483 Incomplete address.

Working with the vendor the carrier, they suspect its in the User
service information -

They want something like this:
                    User Service Information
                        Mandatory Parameter: User service information (29)
                        Pointer to Parameter: 3
                        Parameter Length: 3
                        User service information (-> Q.931
Bearer_capability): 8090a2
                        1... .... = Extension indicator: last octet
                        .00. .... = Coding standard: ITU-T
standardized coding (0x0)
                        ...0 0000 = Information transfer capability:
Speech (0x00)
                        1... .... = Extension indicator: last octet
                        .00. .... = Transfer mode: Circuit mode (0x0)
                        ...1 0000 = Information transfer rate: 64 kbit/s (0x10)
                        1... .... = Extension indicator: last octet
                        .01. .... = Layer identification: Layer 1
identifier (0x1)
                        ...0 0010 = User information layer 1 protocol:
Recommendation G.711 u-law (0x02)


Is there any way to customize this in OpenSIPS?

Sean

Sean



On Tue, Mar 26, 2019 at 1:28 AM Bogdan-Andrei Iancu <[hidden email]> wrote:

>
> Hi Sean,
>
> Where have you got stuck ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
> OpenSIPS Summit 2019
>    https://www.opensips.org/events/Summit-2019Amsterdam/
>
> On 03/22/2019 10:47 PM, Sean Watkins wrote:
> > Hi
> >
> > Are there any SIP-I experts on here that are willing todo some consulting?
> >
> > I need to get a SIP-I to SIP gateway working... I've got partial call
> > connectivity working, but I don't seem to know what I'm doing..
> >
> > Don't get all the ins and outs of reply etc..
> >
> > Sean
> >
> > _______________________________________________
> > Users mailing list
> > [hidden email]
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


--
--
Sean Watkins
403-629-6152

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: sip-i ?

Vlad Patrascu
Hi Sean,

You can set a custom value for any ISUP parameter that appears in the
specification. In your case, you can do:

$isup_param(User Service Information) = "0x8090A2"

Regards,

Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

On 03/26/2019 04:22 PM, Sean Watkins wrote:

> Hi Bogan
>
> I got some more success yesterday with it --  I'll post my configs
> after, for a SIP-I to SIP gateway.
>
> Where I'm stuck now - there seems to be some differences between ANSI
> + ITU. I've got the invite coming into Opensips, then I'm successfully
> adding the SDP info for ISUP. (Whomever came up with this... crazy!)
>
> The far end carrier always drops the calls 483 Incomplete address.
>
> Working with the vendor the carrier, they suspect its in the User
> service information -
>
> They want something like this:
>                      User Service Information
>                          Mandatory Parameter: User service information (29)
>                          Pointer to Parameter: 3
>                          Parameter Length: 3
>                          User service information (-> Q.931
> Bearer_capability): 8090a2
>                          1... .... = Extension indicator: last octet
>                          .00. .... = Coding standard: ITU-T
> standardized coding (0x0)
>                          ...0 0000 = Information transfer capability:
> Speech (0x00)
>                          1... .... = Extension indicator: last octet
>                          .00. .... = Transfer mode: Circuit mode (0x0)
>                          ...1 0000 = Information transfer rate: 64 kbit/s (0x10)
>                          1... .... = Extension indicator: last octet
>                          .01. .... = Layer identification: Layer 1
> identifier (0x1)
>                          ...0 0010 = User information layer 1 protocol:
> Recommendation G.711 u-law (0x02)
>
>
> Is there any way to customize this in OpenSIPS?
>
> Sean
>
> Sean
>
>
>
> On Tue, Mar 26, 2019 at 1:28 AM Bogdan-Andrei Iancu <[hidden email]> wrote:
>> Hi Sean,
>>
>> Where have you got stuck ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>     https://www.opensips-solutions.com
>> OpenSIPS Summit 2019
>>     https://www.opensips.org/events/Summit-2019Amsterdam/
>>
>> On 03/22/2019 10:47 PM, Sean Watkins wrote:
>>> Hi
>>>
>>> Are there any SIP-I experts on here that are willing todo some consulting?
>>>
>>> I need to get a SIP-I to SIP gateway working... I've got partial call
>>> connectivity working, but I don't seem to know what I'm doing..
>>>
>>> Don't get all the ins and outs of reply etc..
>>>
>>> Sean
>>>
>>> _______________________________________________
>>> Users mailing list
>>> [hidden email]
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> --
> --
> Sean Watkins
> 403-629-6152
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: sip-i ?

James Sharp
I’m working on adding proper ANSI ISUP support to opensips.

Sent from my iPhone

> On Mar 26, 2019, at 10:18 AM, Vlad Patrascu <[hidden email]> wrote:
>
> Hi Sean,
>
> You can set a custom value for any ISUP parameter that appears in the specification. In your case, you can do:
>
> $isup_param(User Service Information) = "0x8090A2"
>
> Regards,
>
> Vlad Patrascu
> OpenSIPS Developer
> http://www.opensips-solutions.com
>
>> On 03/26/2019 04:22 PM, Sean Watkins wrote:
>> Hi Bogan
>>
>> I got some more success yesterday with it --  I'll post my configs
>> after, for a SIP-I to SIP gateway.
>>
>> Where I'm stuck now - there seems to be some differences between ANSI
>> + ITU. I've got the invite coming into Opensips, then I'm successfully
>> adding the SDP info for ISUP. (Whomever came up with this... crazy!)
>>
>> The far end carrier always drops the calls 483 Incomplete address.
>>
>> Working with the vendor the carrier, they suspect its in the User
>> service information -
>>
>> They want something like this:
>>                     User Service Information
>>                         Mandatory Parameter: User service information (29)
>>                         Pointer to Parameter: 3
>>                         Parameter Length: 3
>>                         User service information (-> Q.931
>> Bearer_capability): 8090a2
>>                         1... .... = Extension indicator: last octet
>>                         .00. .... = Coding standard: ITU-T
>> standardized coding (0x0)
>>                         ...0 0000 = Information transfer capability:
>> Speech (0x00)
>>                         1... .... = Extension indicator: last octet
>>                         .00. .... = Transfer mode: Circuit mode (0x0)
>>                         ...1 0000 = Information transfer rate: 64 kbit/s (0x10)
>>                         1... .... = Extension indicator: last octet
>>                         .01. .... = Layer identification: Layer 1
>> identifier (0x1)
>>                         ...0 0010 = User information layer 1 protocol:
>> Recommendation G.711 u-law (0x02)
>>
>>
>> Is there any way to customize this in OpenSIPS?
>>
>> Sean
>>
>> Sean
>>
>>
>>
>>> On Tue, Mar 26, 2019 at 1:28 AM Bogdan-Andrei Iancu <[hidden email]> wrote:
>>> Hi Sean,
>>>
>>> Where have you got stuck ?
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>    https://www.opensips-solutions.com
>>> OpenSIPS Summit 2019
>>>    https://www.opensips.org/events/Summit-2019Amsterdam/
>>>
>>>> On 03/22/2019 10:47 PM, Sean Watkins wrote:
>>>> Hi
>>>>
>>>> Are there any SIP-I experts on here that are willing todo some consulting?
>>>>
>>>> I need to get a SIP-I to SIP gateway working... I've got partial call
>>>> connectivity working, but I don't seem to know what I'm doing..
>>>>
>>>> Don't get all the ins and outs of reply etc..
>>>>
>>>> Sean
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> [hidden email]
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> --
>> --
>> Sean Watkins
>> 403-629-6152
>>
>> _______________________________________________
>> Users mailing list
>> [hidden email]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: sip-i ?

Sean Watkins
In reply to this post by Vlad Patrascu
Hi Vlad

So I actually want User service info to look like your code:

    User Service Information
        Mandatory Parameter: User service information (29)
        Pointer to Parameter: 3
        Parameter Length: 3
        User service information (-> Q.931 Bearer_capability): 8090a2
        1... .... = Extension indicator: last octet
        .00. .... = Coding standard: ITU-T standardized coding (0x0)
        ...0 0000 = Information transfer capability: Speech (0x00)
        1... .... = Extension indicator: last octet
        .00. .... = Transfer mode: Circuit mode (0x0)
        ...1 0000 = Information transfer rate: 64 kbit/s (0x10)
        1... .... = Extension indicator: last octet
        .01. .... = Layer identification: Layer 1 identifier (0x1)
        ...0 0010 = User information layer 1 protocol: Recommendation
G.711 u-law (0x02)


Putting this in the config:

           $isup_param(User Service Information) = "0x8090A2";

I wind up getting this for user service info --

User Service Information
    Mandatory Parameter: User service information (29)
    Pointer to Parameter: 3
    Parameter Length: 8
    User service information (-> Q.931 Bearer_capability): 8490411407700000
    1... .... = Extension indicator: last octet
    .00. .... = Coding standard: ITU-T standardized coding (0x0)
    ...0 0100 = Information transfer capability: Unknown (0x04)
    1... .... = Extension indicator: last octet
    .00. .... = Transfer mode: Circuit mode (0x0)
    ...1 0000 = Information transfer rate: 64 kbit/s (0x10)
    0... .... = Extension indicator: information continues through the
next octet
    .10. .... = Layer identification: Layer 2 identifier (0x2)
    ...0 0001 = User information layer 2 protocol: Basic mode ISO 1745 (0x01)
    .00. .... = Mode: Unknown (0x0)
    .000 0111 = Window size: octet & 0x7F7 k
    0... .... = Extension indicator: information continues through the
next octet
    .11. .... = Layer identification: Layer 3 identifier (0x3)
    ...1 0000 = User information layer 3 protocol: User-specified (0x10)
    .... 0001 = Default packet size: 1 octet

Which isn't correct -- funny enough, the default is this:

User Service Information
    Mandatory Parameter: User service information (29)
    Pointer to Parameter: 3
    Parameter Length: 7
    User service information (-> Q.931 Bearer_capability): 03904471000700
    0... .... = Extension indicator: information continues through the
next octet
    .00. .... = Coding standard: ITU-T standardized coding (0x0)
    ...0 0011 = Information transfer capability: Unknown (0x03)
    .0.. .... = Out-band negotiation: Not possible
    0... .... = Extension indicator: information continues through the
next octet
    .10. .... = Transfer mode: Packet mode (0x2)
    ...0 0100 = Information transfer rate: Unknown (0x04)
    0... .... = Extension indicator: information continues through the
next octet
    .11. .... = Layer identification: Layer 3 identifier (0x3)
    ...1 0001 = User information layer 3 protocol: Unknown (0x11)

Any ideas?

Adding some debugging.. I see this:

                xlog ("User Service Information = $isup_param(User
Service Information)");

.. in the log:

Mar 26 15:48:22 TBI-OpenSIPS-1 /usr/sbin/opensips[9036]: Outbound CPN
Address = X
Mar 26 15:48:22 TBI-OpenSIPS-1 /usr/sbin/opensips[9036]: Outbound CPN NOA = 4
Mar 26 15:48:22 TBI-OpenSIPS-1 /usr/sbin/opensips[9036]: Outbound CPN
Numbering Plan= 1
Mar 26 15:48:22 TBI-OpenSIPS-1 /usr/sbin/opensips[9036]: Outbound CGN
Address = X
Mar 26 15:48:22 TBI-OpenSIPS-1 /usr/sbin/opensips[9036]: Outbound CGN NOA = 3
Mar 26 15:48:22 TBI-OpenSIPS-1 /usr/sbin/opensips[9036]: Nature of
connection indicators =  0x10
Mar 26 15:48:22 TBI-OpenSIPS-1 /usr/sbin/opensips[9036]: User Service
Information = 0x8090a2

So something isn't copying over correctly?

Sean

On Tue, Mar 26, 2019 at 11:23 AM Vlad Patrascu <[hidden email]> wrote:

>
> Hi Sean,
>
> You can set a custom value for any ISUP parameter that appears in the
> specification. In your case, you can do:
>
> $isup_param(User Service Information) = "0x8090A2"
>
> Regards,
>
> Vlad Patrascu
> OpenSIPS Developer
> http://www.opensips-solutions.com
>
> On 03/26/2019 04:22 PM, Sean Watkins wrote:
> > Hi Bogan
> >
> > I got some more success yesterday with it --  I'll post my configs
> > after, for a SIP-I to SIP gateway.
> >
> > Where I'm stuck now - there seems to be some differences between ANSI
> > + ITU. I've got the invite coming into Opensips, then I'm successfully
> > adding the SDP info for ISUP. (Whomever came up with this... crazy!)
> >
> > The far end carrier always drops the calls 483 Incomplete address.
> >
> > Working with the vendor the carrier, they suspect its in the User
> > service information -
> >
> > They want something like this:
> >                      User Service Information
> >                          Mandatory Parameter: User service information (29)
> >                          Pointer to Parameter: 3
> >                          Parameter Length: 3
> >                          User service information (-> Q.931
> > Bearer_capability): 8090a2
> >                          1... .... = Extension indicator: last octet
> >                          .00. .... = Coding standard: ITU-T
> > standardized coding (0x0)
> >                          ...0 0000 = Information transfer capability:
> > Speech (0x00)
> >                          1... .... = Extension indicator: last octet
> >                          .00. .... = Transfer mode: Circuit mode (0x0)
> >                          ...1 0000 = Information transfer rate: 64 kbit/s (0x10)
> >                          1... .... = Extension indicator: last octet
> >                          .01. .... = Layer identification: Layer 1
> > identifier (0x1)
> >                          ...0 0010 = User information layer 1 protocol:
> > Recommendation G.711 u-law (0x02)
> >
> >
> > Is there any way to customize this in OpenSIPS?
> >
> > Sean
> >
> > Sean
> >
> >
> >
> > On Tue, Mar 26, 2019 at 1:28 AM Bogdan-Andrei Iancu <[hidden email]> wrote:
> >> Hi Sean,
> >>
> >> Where have you got stuck ?
> >>
> >> Regards,
> >>
> >> Bogdan-Andrei Iancu
> >>
> >> OpenSIPS Founder and Developer
> >>     https://www.opensips-solutions.com
> >> OpenSIPS Summit 2019
> >>     https://www.opensips.org/events/Summit-2019Amsterdam/
> >>
> >> On 03/22/2019 10:47 PM, Sean Watkins wrote:
> >>> Hi
> >>>
> >>> Are there any SIP-I experts on here that are willing todo some consulting?
> >>>
> >>> I need to get a SIP-I to SIP gateway working... I've got partial call
> >>> connectivity working, but I don't seem to know what I'm doing..
> >>>
> >>> Don't get all the ins and outs of reply etc..
> >>>
> >>> Sean
> >>>
> >>> _______________________________________________
> >>> Users mailing list
> >>> [hidden email]
> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> > --
> > --
> > Sean Watkins
> > 403-629-6152
> >
> > _______________________________________________
> > Users mailing list
> > [hidden email]
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



--
--
Sean Watkins
403-629-6152

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users