Hello guys,
I have an issue with SIP public provider when internal user is forwarded to another internal user.
Architecture: OXE L2.300.33 <-SIP ISDN-> Audiocodes E-SBC <-SIP-> Public provider
I am using normal DDI translation working fine for inbound/outbound calls (DDI manipulation on OXE side not SBC).
Scenario: internal OXE user 1111 is imm fwd to 1000. For external call from PSTN on 1111 ext DDI (xxxxxxx), OXE replies with:
SIP/2.0 302 Moved Temporarily
Contact: <sip:1000@192.168.2.240;user=phone>
User-Agent: OmniPCX Enterprise R11.2.2 l2.300.33.a
To: <sip:externalddi@192.168.2.240:5061>;tag=7426ebac5b613540336b97c4e514add5
From: <sip:extcallingnb@tel.t-online.de;user=phone>;tag=1c296624339
Call-ID: 296596573742017183031@192.168.2.250
CSeq: 1 INVITE
Via: SIP/2.0/TCP 192.168.2.250:5061;alias;branch=z9hG4bKac296892219
Content-Length: 0
192.168.2.240 OXE IP address
192.168.2.250 SBC address and remote domain in SIP ext gw config
Of course that is sent also by SBC to provider. I would expect the contact to present external DDI and not internal number.
Any way to achieve this w/o manipulation on SBC?
(wrap up: DDI translation should work in my view for moved temporarily Contact header... - did not test yet moved permanently)
Any comment is appreciated.
302 Moved Temporarily contact manipulation
Re: 302 Moved Temporarily contact manipulation
suggestion 1:
- maybe the call is not sorted to the right sip external gw? An external Provider-Call will be handled as incoming call to the default SIP TrunkGroup. Since this is most of the time an ABCF SIP TrunkGroup, diversions will be handled with 302 Moved Temporarly Message. Can you attach an "motortrace 3; traced" output, please? (I think in default the OXE SIP Motor will use the To sip uri host-name (in your case - tel.t-online.de) into account for decision of the ext. GW.
suggestion 2:
- there is a new software switch in sip ext gw parameters. it's called "Support redirection response". as per docs it can spent 302 Moved Temporarly Message for ISDF SIP Trunk Group too. But only for external forwarded calls... (side 345 in doc "8AL91007USAG - Ed. 01 - April 2017 - IP-PCX Networks")
regards...
- maybe the call is not sorted to the right sip external gw? An external Provider-Call will be handled as incoming call to the default SIP TrunkGroup. Since this is most of the time an ABCF SIP TrunkGroup, diversions will be handled with 302 Moved Temporarly Message. Can you attach an "motortrace 3; traced" output, please? (I think in default the OXE SIP Motor will use the To sip uri host-name (in your case - tel.t-online.de) into account for decision of the ext. GW.
suggestion 2:
- there is a new software switch in sip ext gw parameters. it's called "Support redirection response". as per docs it can spent 302 Moved Temporarly Message for ISDF SIP Trunk Group too. But only for external forwarded calls... (side 345 in doc "8AL91007USAG - Ed. 01 - April 2017 - IP-PCX Networks")
regards...
--- back to basics... focus your eyes to the essential things... ---
- tot3nkopf
- Alcatel Unleashed Certified Guru
- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: 302 Moved Temporarily contact manipulation
Yes, changing the main gw IP to the ISDN trunk solves the issue (with no moved temp however).tgn wrote: ↑09 Apr 2017 09:55 suggestion 1:
- maybe the call is not sorted to the right sip external gw? An external Provider-Call will be handled as incoming call to the default SIP TrunkGroup. Since this is most of the time an ABCF SIP TrunkGroup, diversions will be handled with 302 Moved Temporarly Message. Can you attach an "motortrace 3; traced" output, please? (I think in default the OXE SIP Motor will use the To sip uri host-name (in your case - tel.t-online.de) into account for decision of the ext. GW.
Strange that the ext gw as destination is not identified by OXE in first case (destination from SBC is the ext gw with different port from 5060 - main SIP gw port)
See the invite from SBC:
Code: Select all
INVITE sip:49XXXXXXXX@192.168.2.240:5061 SIP/2.0
Via: SIP/2.0/TCP 192.168.2.250:5061;alias;branch=z9hG4bKac1743050083
Max-Forwards: 61
From: <sip:49XXXXXXXX@tel.t-online.de;user=phone>;tag=1c1742825757
To: <sip:49XXXXXXXXX@192.168.2.240:5061>
Call-ID: 174279799784201703336@192.168.2.250
CSeq: 1 INVITE
Contact: <sip:+49XXXXXXXXX@192.168.2.250:5061;transport=tcp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Supported: 100rel,timer,resource-priority
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INFO, INVITE, ACK, OPTIONS, CANCEL, BYE
Session-Expires: 1800
Min-Se: 900
User-Agent: AudiocodesSBC/v.6.80A.244.006
P-Asserted-Identity: <sip:49XXXXXXXXX@tel.t-online.de;user=phone>
Accept: application/isup
Accept: application/xml
Accept: application/media_control+xml
Accept: application/vnd.etsi.cug+xml
Accept: application/vnd.etsi.sci+xml
Accept: application/sdp
Content-Type: application/sdp
Content-Length: 210
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Session-ID: 3fee1e9e44988e69abd93097a13582f7
v=0
o=- 1980706870 3194015747 IN IP4 217.0.23.100
s=IMSS
c=IN IP4 217.0.4.167
t=0 0
m=audio 8572 RTP/AVP 8 101 18
Port 5061 port for ext SIP gw
I have read about it already and I will test it.tgn wrote: ↑09 Apr 2017 09:55 suggestion 2:
- there is a new software switch in sip ext gw parameters. it's called "Support redirection response". as per docs it can spent 302 Moved Temporarly Message for ISDF SIP Trunk Group too. But only for external forwarded calls... (side 345 in doc "8AL91007USAG - Ed. 01 - April 2017 - IP-PCX Networks")
regards...
Thank you tgn.