Hi all,
I am installing my first FusionPBX. Everything seems to work except for the outbound Caller ID. When i do an outbound call, i see in the SIP packet:
INVITE sip:003112345678@xx.xx.xx.xx SIP/2.0
From: "200" <sip:200@yy.yy.yy.yy>;tag=epv1KUU22X79j
Where xx.xx.xx.xx is the ip of my trunk provider and yy.yy.yy.yy is the ip of my FusionpBX server.
Obviously "200" <sip:200@ is an incorrect caller ID and my trunk provider ignores this header (and should!).
In my gateway configuration i have set "Caller ID In From" to True and in my extension configuration both Effective Caller ID Number and Outbound Caller ID Name are "003187654321"
My gateway and extension are both in context test.voip.domain.nl and my outbound route is in context public.
When i change in my outbound route effective_caller_id_number=${outbound_caller_id_number} to effective_caller_id_number=003187654321 (a static CID), then it works prefectly, but i dont think it would work like that.
Who can help me with this (seemingly small) issue.
Thank you VERY much!
Regards,
Jeroen Hermans
I am installing my first FusionPBX. Everything seems to work except for the outbound Caller ID. When i do an outbound call, i see in the SIP packet:
INVITE sip:003112345678@xx.xx.xx.xx SIP/2.0
From: "200" <sip:200@yy.yy.yy.yy>;tag=epv1KUU22X79j
Where xx.xx.xx.xx is the ip of my trunk provider and yy.yy.yy.yy is the ip of my FusionpBX server.
Obviously "200" <sip:200@ is an incorrect caller ID and my trunk provider ignores this header (and should!).
In my gateway configuration i have set "Caller ID In From" to True and in my extension configuration both Effective Caller ID Number and Outbound Caller ID Name are "003187654321"
My gateway and extension are both in context test.voip.domain.nl and my outbound route is in context public.
When i change in my outbound route effective_caller_id_number=${outbound_caller_id_number} to effective_caller_id_number=003187654321 (a static CID), then it works prefectly, but i dont think it would work like that.
Who can help me with this (seemingly small) issue.
Thank you VERY much!
Regards,
Jeroen Hermans