Thread: Re: [OpenSIPStack] INVITE not allowing to pass throught OSBC
Brought to you by:
joegenbaclor
Menu
▾
▴
opensipstack-devel
|
From: <sa...@ER...> - 2007-12-01 00:53:37
|
Hi OpenSBC is NOT allowing the INVITE from a phone registered on SIPxchange = to pass through it because it is attempting to authenticate the user who made the call = (From:). We need to make some configuration changes on OpenSBC before the INVITE = will be passed to our ITSP. Can you show me how to do this? Warren Kreckler |
|
From: Joegen E. B. <joe...@gm...> - 2007-12-01 08:07:06
|
Look for the "Trusted Domains" section in the Config Pages. Put a check on the "Accept All Calls" box or you may add the domain of SIPX in the trusted domain list. hth Joegen sales@ER wrote: > Hi > > OpenSBC is NOT allowing the INVITE from a phone registered on SIPxchange to pass through it > because it is attempting to authenticate the user who made the call (From:). > We need to make some configuration changes on OpenSBC before the INVITE will > be passed to our ITSP. > > Can you show me how to do this? > > > Warren Kreckler > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
|
From: <sa...@ER...> - 2007-12-01 18:33:49
|
Hi How do i chage opensbc so i can use the web interface from any computer on or off the network Warren Kreckler |
|
From: <jo...@op...> - 2007-12-02 00:38:41
|
I am not very sure if I get your question right but the web interface of OpenSBC is accessible from any computer in the network via HTTP port 9999 of the IP address of where OpenSBC is installed http://opensbc_ip_address:9999 Please give more information if this is not what you meant. Joegen sales@ER wrote: > Hi > > How do i chage opensbc so i can use the web interface from any computer on > or off the network > > Warren Kreckler > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > |
|
From: <sa...@ER...> - 2007-12-02 12:23:51
|
Hi Yes i understand that. From three different location in the USA thousands of miles apart and we can't access. One doc i read it states from the computer that opensbc is installed on, which i take to mean literally. But i do remember in the last version before this latest update i was able to access from a network computer. I know it does not make sense but there you are. I am using the CVS lastest from last Wednesday. Warren Kreckler ----- Original Message ----- From: "jo...@op..." <joe...@gm...> To: <ope...@li...> Sent: Saturday, December 01, 2007 6:38 PM Subject: Re: [OpenSIPStack] Web Interface Question > I am not very sure if I get your question right but the web interface of > OpenSBC is accessible from any computer in the network via HTTP port > 9999 of the IP address of where OpenSBC is installed > > http://opensbc_ip_address:9999 > > Please give more information if this is not what you meant. > > Joegen > > sales@ER wrote: > > Hi > > > > How do i chage opensbc so i can use the web interface from any computer on > > or off the network > > > > Warren Kreckler > > > > > > > > ------------------------------------------------------------------------- > > SF.Net email is sponsored by: The Future of Linux Business White Paper > > from Novell. From the desktop to the data center, Linux is going > > mainstream. Let it simplify your IT future. > > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > > _______________________________________________ > > opensipstack-devel mailing list > > ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > > > > > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
|
From: Joegen E. B. <joe...@gm...> - 2007-12-03 00:50:03
|
I can assure you that HTTP Admin maybe accesses from anywhere in the internet as long as the host where OpenSBC is installed allow remote connection to the http port (TCP 9999). You might want to look at the possibility that this is a firewall/security issue rather than a software issue. sales@ER wrote: > Hi > > Yes i understand that. From three different location in the USA thousands > of miles apart and we can't access. One doc i read it states from the > computer that opensbc is installed on, which i take to mean literally. But > i do remember in the last version before this latest update i was able to > access from a network computer. I know it does not make sense but there you > are. I am using the CVS lastest from last Wednesday. > > Warren Kreckler > > > ----- Original Message ----- > From: "jo...@op..." <joe...@gm...> > To: <ope...@li...> > Sent: Saturday, December 01, 2007 6:38 PM > Subject: Re: [OpenSIPStack] Web Interface Question > > > >> I am not very sure if I get your question right but the web interface of >> OpenSBC is accessible from any computer in the network via HTTP port >> 9999 of the IP address of where OpenSBC is installed >> >> http://opensbc_ip_address:9999 >> >> Please give more information if this is not what you meant. >> >> Joegen >> >> sales@ER wrote: >> >>> Hi >>> >>> How do i chage opensbc so i can use the web interface from any computer >>> > on > >>> or off the network >>> >>> Warren Kreckler >>> >>> >>> >>> >> ------------------------------------------------------------------------- >> >>> SF.Net email is sponsored by: The Future of Linux Business White Paper >>> from Novell. From the desktop to the data center, Linux is going >>> mainstream. Let it simplify your IT future. >>> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 >>> _______________________________________________ >>> opensipstack-devel mailing list >>> ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel >>> >>> >>> >>> >>> >> ------------------------------------------------------------------------- >> SF.Net email is sponsored by: The Future of Linux Business White Paper >> from Novell. From the desktop to the data center, Linux is going >> mainstream. Let it simplify your IT future. >> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 >> _______________________________________________ >> opensipstack-devel mailing list >> ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel >> > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
|
From: <sa...@ER...> - 2007-12-05 02:38:24
|
Hi Is there a way to eliminate all but one VIA in the INVITE? Warren Kreckler |
|
From: Joegen E. B. <joe...@gm...> - 2007-12-05 03:02:26
|
Vias are inserted by proxies so that they remain in the signaling path for responses. So unless you wan't to open a really big can of worms by removing vias inserted by proxies it is not a good idea. If your question was how to remove the vias programatically then thats definitely doable. Via via; invite.GetViaAt( via, 0 ); invite.RemoveAllVias(); invite.AppendVia( via ); sales@ER wrote: > Hi > > Is there a way to eliminate all but one VIA in the INVITE? > > Warren Kreckler > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
|
From: <sa...@ER...> - 2007-12-05 04:13:39
|
Hi Our ITSP can accept only 1 Via statement in an INVITE. The INVITE when it reaches the SBC has an entry from the phone and two from sipx. I cannot find any documentation about an option to remove Via Headers. Warren Kreckler ----- Original Message ----- From: "Joegen E. Baclor" <joe...@gm...> To: <ope...@li...> Cc: <jo...@op...> Sent: Tuesday, December 04, 2007 9:02 PM Subject: Re: [OpenSIPStack] INVITE and multi via: > Vias are inserted by proxies so that they remain in the signaling path > for responses. So unless you wan't to open a really big can of worms > by removing vias inserted by proxies it is not a good idea. If your > question was how to remove the vias programatically then thats > definitely doable. > > Via via; > invite.GetViaAt( via, 0 ); > invite.RemoveAllVias(); > invite.AppendVia( via ); > > sales@ER wrote: > > Hi > > > > Is there a way to eliminate all but one VIA in the INVITE? > > > > Warren Kreckler > > > > > > ------------------------------------------------------------------------- > > SF.Net email is sponsored by: The Future of Linux Business White Paper > > from Novell. From the desktop to the data center, Linux is going > > mainstream. Let it simplify your IT future. > > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > > _______________________________________________ > > opensipstack-devel mailing list > > ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > > > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
|
From: <jo...@op...> - 2007-12-05 04:21:04
|
Hi Warren, If the call flow is Caller->sipX->SBC->ITSP, then OpenSBC would have just sent a single via. Is your call flow Caller->SBC->sipX->ITSP? Joegen sales@ER wrote: > Hi > > Our ITSP can accept only 1 Via statement in an INVITE. The INVITE when it > reaches the SBC has an entry from the phone and two from sipx. I cannot find > any documentation about an option to remove Via Headers. > > Warren Kreckler > > > ----- Original Message ----- > From: "Joegen E. Baclor" <joe...@gm...> > To: <ope...@li...> > Cc: <jo...@op...> > Sent: Tuesday, December 04, 2007 9:02 PM > Subject: Re: [OpenSIPStack] INVITE and multi via: > > > >> Vias are inserted by proxies so that they remain in the signaling path >> for responses. So unless you wan't to open a really big can of worms >> by removing vias inserted by proxies it is not a good idea. If your >> question was how to remove the vias programatically then thats >> definitely doable. >> >> Via via; >> invite.GetViaAt( via, 0 ); >> invite.RemoveAllVias(); >> invite.AppendVia( via ); >> >> sales@ER wrote: >> >>> Hi >>> >>> Is there a way to eliminate all but one VIA in the INVITE? >>> >>> Warren Kreckler >>> >>> >>> >> ------------------------------------------------------------------------- >> >>> SF.Net email is sponsored by: The Future of Linux Business White Paper >>> from Novell. From the desktop to the data center, Linux is going >>> mainstream. Let it simplify your IT future. >>> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 >>> _______________________________________________ >>> opensipstack-devel mailing list >>> ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel >>> >>> >>> >>> >> ------------------------------------------------------------------------- >> SF.Net email is sponsored by: The Future of Linux Business White Paper >> from Novell. From the desktop to the data center, Linux is going >> mainstream. Let it simplify your IT future. >> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 >> _______________________________________________ >> opensipstack-devel mailing list >> ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel >> > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > |
|
From: eric h. <er...@so...> - 2007-12-05 04:50:32
|
jo...@op... wrote: > Hi Warren, > > If the call flow is Caller->sipX->SBC->ITSP, then OpenSBC would have > just sent a single via. Is your call flow Caller->SBC->sipX->ITSP? > > We are working on publishing a How To guide for using OSBC with SIPX. But until that is ready, think about using SIPX as a gateway for all PSTN-bound calls so that the call flow would be as follows: UA->OSBC->SIPX->OSBC->ITSP. Since OSBC will be proxying the media for NAT traversal in most cases, having OSBC as a single IP address (for both signaling and media) known to your ITSP will simplify their configuration as well. > Joegen > > sales@ER wrote: > >> Hi >> >> Our ITSP can accept only 1 Via statement in an INVITE. The INVITE when it >> reaches the SBC has an entry from the phone and two from sipx. I cannot find >> any documentation about an option to remove Via Headers. >> >> Warren Kreckler >> >> > |
|
From: eric h. <er...@so...> - 2007-12-05 04:59:59
|
Correction... eric hernaez wrote: > jo...@op... wrote: > >> Hi Warren, >> >> If the call flow is Caller->sipX->SBC->ITSP, then OpenSBC would have >> just sent a single via. Is your call flow Caller->SBC->sipX->ITSP? >> >> >> > > We are working on publishing a How To guide for using OSBC with SIPX. > But until that is ready, think about using SIPX as a gateway for all > PSTN-bound calls so that the call flow would be as follows: > UA->OSBC->SIPX->OSBC->ITSP. > > I meant to write: think about using OSBC as a gateway for all PSTN-bound calls > Since OSBC will be proxying the media for NAT traversal in most cases, > having OSBC as a single IP address (for both signaling and media) known > to your ITSP will simplify their configuration as well. > > > > |
|
From: <sa...@ER...> - 2007-12-05 05:04:02
|
Hi eric Yes, UA->OSBC->SIPX->OSBC->ITSP. In our case we are using sip truck as gateway. ITSP have different Invite requirement mainly attributed to their security concerns. Good luck with your guide Warren Kreckler ----- Original Message ----- From: "eric hernaez" <er...@so...> To: <ope...@li...> Sent: Tuesday, December 04, 2007 10:55 PM Subject: Re: [OpenSIPStack] INVITE and multi via: > > > jo...@op... wrote: > > Hi Warren, > > > > If the call flow is Caller->sipX->SBC->ITSP, then OpenSBC would have > > just sent a single via. Is your call flow Caller->SBC->sipX->ITSP? > > > > > > We are working on publishing a How To guide for using OSBC with SIPX. > But until that is ready, think about using SIPX as a gateway for all > PSTN-bound calls so that the call flow would be as follows: > UA->OSBC->SIPX->OSBC->ITSP. > > Since OSBC will be proxying the media for NAT traversal in most cases, > having OSBC as a single IP address (for both signaling and media) known > to your ITSP will simplify their configuration as well. > > > > Joegen > > > > sales@ER wrote: > > > >> Hi > >> > >> Our ITSP can accept only 1 Via statement in an INVITE. The INVITE when it > >> reaches the SBC has an entry from the phone and two from sipx. I cannot find > >> any documentation about an option to remove Via Headers. > >> > >> Warren Kreckler > >> > >> > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
|
From: <sa...@ER...> - 2007-12-05 05:19:40
|
Hi eric Yes, UA->OSBC->SIPX->OSBC->ITSP. We are determine to use OSBC with sipX. At this point it seems very dueable but it's the choice of ITSP that will be the stumbling block. OSBC needs an admin screen to minipulate the INVITE to tailor them to various ITSP requirements. Good Luck with your guide Warren Kreckler ----- Original Message ----- From: "eric hernaez" <er...@so...> To: <ope...@li...> Sent: Tuesday, December 04, 2007 10:55 PM Subject: Re: [OpenSIPStack] INVITE and multi via: > > > jo...@op... wrote: > > Hi Warren, > > > > If the call flow is Caller->sipX->SBC->ITSP, then OpenSBC would have > > just sent a single via. Is your call flow Caller->SBC->sipX->ITSP? > > > > > > We are working on publishing a How To guide for using OSBC with SIPX. > But until that is ready, think about using SIPX as a gateway for all > PSTN-bound calls so that the call flow would be as follows: > UA->OSBC->SIPX->OSBC->ITSP. > > Since OSBC will be proxying the media for NAT traversal in most cases, > having OSBC as a single IP address (for both signaling and media) known > to your ITSP will simplify their configuration as well. > > > > Joegen > > > > sales@ER wrote: > > > >> Hi > >> > >> Our ITSP can accept only 1 Via statement in an INVITE. The INVITE when it > >> reaches the SBC has an entry from the phone and two from sipx. I cannot find > >> any documentation about an option to remove Via Headers. > >> > >> Warren Kreckler > >> > >> > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
|
From: <sa...@ER...> - 2007-12-05 04:52:40
|
332415:31:42.035 DBG: [CID=0x06eb] INVITE sip:3277096@204.16.99.202;transport=udp;user=phone SIP/2.0 332415:31:42.035 DBG: [CID=0x06eb] From: "warren kreckler" <sip:773...@si...>;tag=9d0541d4bf80e258 332415:31:42.035 DBG: [CID=0x06eb] To: <sip:32...@si...;user=phone> 332415:31:42.035 DBG: [CID=0x06eb] Via: SIP/2.0/UDP 69.98.187.241:5080;branch=z9hG4bK-7c7323b52db90a047a77417f3acbb045 332415:31:42.035 DBG: [CID=0x06eb] Via: SIP/2.0/UDP 69.98.187.241;branch=z9hG4bK-fe93ff6b4b3aaa12dd017652ff4952c1 332415:31:42.035 DBG: [CID=0x06eb] Via: SIP/2.0/UDP 69.98.187.240:5060;iid=2562;branch=z9hG4bK3c36138422a0dc11936990b82ee269d3-9 07ceb9e2698906b33bcd9a029bcd8de;uas-addr=69.98.187.241;rport=5060 332415:31:42.035 DBG: [CID=0x06eb] Via: SIP/2.0/UDP 69.98.187.226;branch=z9hG4bK6ea99cc86b68e1a7;rport=5060;received=69.38.187.2 26 332415:31:42.035 DBG: [CID=0x06eb] CSeq: 21659 INVITE ----- Original Message ----- From: "jo...@op..." <joe...@gm...> To: <ope...@li...> Sent: Tuesday, December 04, 2007 10:21 PM Subject: Re: [OpenSIPStack] INVITE and multi via: > Hi Warren, > > If the call flow is Caller->sipX->SBC->ITSP, then OpenSBC would have > just sent a single via. Is your call flow Caller->SBC->sipX->ITSP? > > Joegen > > sales@ER wrote: > > Hi > > > > Our ITSP can accept only 1 Via statement in an INVITE. The INVITE when it > > reaches the SBC has an entry from the phone and two from sipx. I cannot find > > any documentation about an option to remove Via Headers. > > > > Warren Kreckler > > > > > > ----- Original Message ----- > > From: "Joegen E. Baclor" <joe...@gm...> > > To: <ope...@li...> > > Cc: <jo...@op...> > > Sent: Tuesday, December 04, 2007 9:02 PM > > Subject: Re: [OpenSIPStack] INVITE and multi via: > > > > > > > >> Vias are inserted by proxies so that they remain in the signaling path > >> for responses. So unless you wan't to open a really big can of worms > >> by removing vias inserted by proxies it is not a good idea. If your > >> question was how to remove the vias programatically then thats > >> definitely doable. > >> > >> Via via; > >> invite.GetViaAt( via, 0 ); > >> invite.RemoveAllVias(); > >> invite.AppendVia( via ); > >> > >> sales@ER wrote: > >> > >>> Hi > >>> > >>> Is there a way to eliminate all but one VIA in the INVITE? > >>> > >>> Warren Kreckler > >>> > >>> > >>> > >> ------------------------------------------------------------------------- > >> > >>> SF.Net email is sponsored by: The Future of Linux Business White Paper > >>> from Novell. From the desktop to the data center, Linux is going > >>> mainstream. Let it simplify your IT future. > >>> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > >>> _______________________________________________ > >>> opensipstack-devel mailing list > >>> ope...@li... > >>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > >>> > >>> > >>> > >>> > >> ------------------------------------------------------------------------- > >> SF.Net email is sponsored by: The Future of Linux Business White Paper > >> from Novell. From the desktop to the data center, Linux is going > >> mainstream. Let it simplify your IT future. > >> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > >> _______________________________________________ > >> opensipstack-devel mailing list > >> ope...@li... > >> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > >> > > > > > > > > ------------------------------------------------------------------------- > > SF.Net email is sponsored by: The Future of Linux Business White Paper > > from Novell. From the desktop to the data center, Linux is going > > mainstream. Let it simplify your IT future. > > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > > _______________________________________________ > > opensipstack-devel mailing list > > ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > > > > > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
|
From: <sa...@ER...> - 2007-12-06 02:54:14
|
Hi How do you code a rule to replace the From URI. from a host name to an ipaddr? Warren Kreckler |
|
From: <sa...@ER...> - 2007-12-05 04:12:14
|
Hi Our ITSP can accept only 1 Via statement in an INVITE. The INVITE when it reaches the SBC has an entry from the phone and two from sipx. I cannot find any documentation about an option to remove Via Headers. Warren Kreckler ----- Original Message ----- From: "Joegen E. Baclor" <joe...@gm...> To: <ope...@li...> Cc: <jo...@op...> Sent: Tuesday, December 04, 2007 9:02 PM Subject: Re: [OpenSIPStack] INVITE and multi via: > Vias are inserted by proxies so that they remain in the signaling path > for responses. So unless you wan't to open a really big can of worms > by removing vias inserted by proxies it is not a good idea. If your > question was how to remove the vias programatically then thats > definitely doable. > > Via via; > invite.GetViaAt( via, 0 ); > invite.RemoveAllVias(); > invite.AppendVia( via ); > > sales@ER wrote: > > Hi > > > > Is there a way to eliminate all but one VIA in the INVITE? > > > > Warren Kreckler > > > > > > ------------------------------------------------------------------------- > > SF.Net email is sponsored by: The Future of Linux Business White Paper > > from Novell. From the desktop to the data center, Linux is going > > mainstream. Let it simplify your IT future. > > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > > _______________________________________________ > > opensipstack-devel mailing list > > ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > > > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
|
From: <sa...@ER...> - 2007-12-05 04:15:49
|
Hi Our ITSP can accept only 1 Via statement in an INVITE. The INVITE when it reaches the SBC has an entry from the phone and two from sipx. I cannot find any documentation about an option to remove Via Headers. Warren Kreckler ----- Original Message ----- From: "Joegen E. Baclor" <joe...@gm...> To: <ope...@li...> Cc: <jo...@op...> Sent: Tuesday, December 04, 2007 9:02 PM Subject: Re: [OpenSIPStack] INVITE and multi via: > Vias are inserted by proxies so that they remain in the signaling path > for responses. So unless you wan't to open a really big can of worms > by removing vias inserted by proxies it is not a good idea. If your > question was how to remove the vias programatically then thats > definitely doable. > > Via via; > invite.GetViaAt( via, 0 ); > invite.RemoveAllVias(); > invite.AppendVia( via ); > > sales@ER wrote: > > Hi > > > > Is there a way to eliminate all but one VIA in the INVITE? > > > > Warren Kreckler > > > > > > ------------------------------------------------------------------------- > > SF.Net email is sponsored by: The Future of Linux Business White Paper > > from Novell. From the desktop to the data center, Linux is going > > mainstream. Let it simplify your IT future. > > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > > _______________________________________________ > > opensipstack-devel mailing list > > ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > > > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
|
From: <sa...@ER...> - 2007-12-06 03:06:23
|
Hi I found the solution: Background: In our testing we are using public addressing to allow remove developers to gain easy access to both sipx and opensbc. The 2nd NIC whicd had a private address and was activated was not used but we were wrong opensbc see's the card alive and wants to use it, event thought we set the interface to only use the 1st NIC. Not thinking it was not in play we forgot about it. Problem: We were not able to connect to :9999 to local box but no able to from local or remote networks Solution: Disabled the 2nd NIC card. Warren Kreckler ----- Original Message ----- From: "jo...@op..." <joe...@gm...> To: <ope...@li...> Sent: Saturday, December 01, 2007 6:38 PM Subject: Re: [OpenSIPStack] Web Interface Question > I am not very sure if I get your question right but the web interface of > OpenSBC is accessible from any computer in the network via HTTP port > 9999 of the IP address of where OpenSBC is installed > > http://opensbc_ip_address:9999 > > Please give more information if this is not what you meant. > > Joegen > > sales@ER wrote: > > Hi > > > > How do i chage opensbc so i can use the web interface from any computer on > > or off the network > > > > Warren Kreckler > > > > > > > > ------------------------------------------------------------------------- > > SF.Net email is sponsored by: The Future of Linux Business White Paper > > from Novell. From the desktop to the data center, Linux is going > > mainstream. Let it simplify your IT future. > > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > > _______________________________________________ > > opensipstack-devel mailing list > > ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > > > > > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X