Based upon what you provided, I'm not sure why the GMSC behaved as you indicated. You should be able to obtain the answer from the GMSC administrator or vendor. For instance, there might be service or trust reason to perform the mentioned conversion.
> -----Original Message----- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of souvik pal > Sent: Wednesday, August 06, 2014 4:57 AM > To: sip-implementors@lists.cs.columbia.edu > Subject: [Sip-implementors] FROM header in SIP INVITE > shows:unavailable@unknown.invalid > > Dear Experts, > > We have the following call case: > > Call is originated from PSTN. > > We have GMSC node ( transit switch) which receives an INVITE containing > encapsulated ISUP IAM message in SIP-I interface. > > The GMSC further sends INVITE in SIP interface to the end node (MSS) in > which the FROM header does not contain the calling party number. > > The FROM header is displayed as : > From: <sip:unavailable@unknown.invalid>;tag=2609184897 > > The incoming INVITE towards GMSC contains FROM header containing calling > party number and is displayed as: > > From: <sip:4959516681@10.242.30.10;user=phone>;tag=p9343wwl-CC-23. > > The incoming ISUP IAM message has the following parameters present: > > CgPN ( calling party number):4959516681 > > NOA (nature od Address)=National > > Presentation restricted ind= *Presentation allowed* > > CallingPN incomplete ind = Complete > > Screening ind = Network provided > > Numbering plan ind = ISDN (Telephony) > > Pls help us investigate the reason why FROM header for INVITE sent from > GMSC does not contain calling party number and is displayed as > unavailable@unknown.invalid. > > > Thanks in Advance! > > > Regards, > Souvik Pal > > > > On Tue, Aug 5, 2014 at 2:50 PM, souvik pal <souvik16...@gmail.com> wrote: > > > Dear Team, > > > > We have the following call case: > > > > Call is originated from PSTN. > > > > We have GMSC node ( transit switch) which receives an INVITE > > containing encapsulated ISUP IAM message in SIP-I interface. > > > > The GMSC further sends INVITE in SIP interface to the end node (MSS) > > in which the FROM header does not contain the calling party number. > > > > The FROM header is displayed as : > > From: <sip:unavailable@unknown.invalid>;tag=2609184897 > > > > The incoming INVITE towards GMSC contains FROM header containing > > calling party number and is displayed as: > > > > From: <sip:4959516681@10.242.30.10;user=phone>;tag=p9343wwl-CC-23. > > > > The incoming ISUP IAM message has the following parameters present: > > > > CgPN ( calling party number):4959516681 > > > > NOA (nature od Address)=National > > > > Presentation restricted ind= *Presentation allowed* > > > > CallingPN incomplete ind = Complete > > > > Screening ind = Network provided > > > > Numbering plan ind = ISDN (Telephony) > > > > Pls help us investigate the reason why FROM header for INVITE sent > > from GMSC does not contain calling party number and is displayed as > > unavailable@unknown.invalid. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
