IPO 500 V 4.2(14)
VM Pro 4.2.24
VM Pro Client 4.3(30)
60 IP Sets 4610SW/5610SW
130 Users (Yes we run 24x7)
1 IP 1616
No Upgrade in the near future.
Good day Everyone,
We have been using a SIP trunk for inbound calls now for three or four years. The caller's number from inbound calls is currently displayed as "nnnnnnnnnn:Anonymous". The executive group has asked if the callers name can be displayed in addition to their number.
1. Can 4.2(14) support this? If so please point me top the right help and search topics (terms)in the literature.. I have been unable to locate any information specifically addressing this in the Office Manager, the help file or the pdf.
2. Here is the beginning of a trace of a successful SIP call, it appears to have the necessary information, unless the IPO is looking for the name in the "m:" field instead of the "f:" field..
417875059mS SIP Rx: UDP SIP_Provider's_URL:5060 -> IPO_'s_URL:5060
INVITE sip:8765432109@IPO_'s_URL:5060 SIP/2.0
v: SIP/2.0/UDP SIP_Provider's_URL:5060;branch=z9hG4bKa88e307e00f5f97b528cec1bafb657b0
Max-Forwards: 70
f: Caller's_Name <sip:9012345678@IPO_'s_URL:5060>;tag=187b01397693e0885346a1a515027403
t: <sip:8765432109@IPO_'s_URL:5060>
i: 6883b93b5fb8ac079bfa382182e148f1-68ef2@SIP_Provider's_URL
CSeq: 2543 INVITE
m: Anonymous <sip:SIP_Provider's_URL:5060;transport=udp>
Expires: 300
Should the "m:" field be the one that is providing the information to the IPO 500, I will need to contact the SIP provider to make the change.
Thanks, as always, for your suggestions and observations.
WN
4946
VM Pro 4.2.24
VM Pro Client 4.3(30)
60 IP Sets 4610SW/5610SW
130 Users (Yes we run 24x7)
1 IP 1616
No Upgrade in the near future.
Good day Everyone,
We have been using a SIP trunk for inbound calls now for three or four years. The caller's number from inbound calls is currently displayed as "nnnnnnnnnn:Anonymous". The executive group has asked if the callers name can be displayed in addition to their number.
1. Can 4.2(14) support this? If so please point me top the right help and search topics (terms)in the literature.. I have been unable to locate any information specifically addressing this in the Office Manager, the help file or the pdf.
2. Here is the beginning of a trace of a successful SIP call, it appears to have the necessary information, unless the IPO is looking for the name in the "m:" field instead of the "f:" field..
417875059mS SIP Rx: UDP SIP_Provider's_URL:5060 -> IPO_'s_URL:5060
INVITE sip:8765432109@IPO_'s_URL:5060 SIP/2.0
v: SIP/2.0/UDP SIP_Provider's_URL:5060;branch=z9hG4bKa88e307e00f5f97b528cec1bafb657b0
Max-Forwards: 70
f: Caller's_Name <sip:9012345678@IPO_'s_URL:5060>;tag=187b01397693e0885346a1a515027403
t: <sip:8765432109@IPO_'s_URL:5060>
i: 6883b93b5fb8ac079bfa382182e148f1-68ef2@SIP_Provider's_URL
CSeq: 2543 INVITE
m: Anonymous <sip:SIP_Provider's_URL:5060;transport=udp>
Expires: 300
Should the "m:" field be the one that is providing the information to the IPO 500, I will need to contact the SIP provider to make the change.
Thanks, as always, for your suggestions and observations.
WN
4946